Issue 3237: Python: Naming of POA classes (python-ftf) Source: Humboldt-Universitaet (Mr. Martin von Loewis, loewis@informatik.hu-berlin.de) Nature: Uncategorized Issue Severity: Summary: On page 13 (page 18 in 99-08-02), it says that module M results in a Python package M__POA containing the skeletons. In the next paragraph, it refers to the package POA_M. They can't both be right. In omniORBpy I use POA_M, since that is what the C++ mapping does. Resolution: The specification is correct, the example is wrong Revised Text: Replace POA_M.I with M__POA.I Actions taken: January 19, 2000: received issue October 10, 2000: closed isue Discussion: End of Annotations:===== Date: Wed, 19 Jan 2000 16:21:35 +0100 Message-Id: <200001191521.QAA25715@pandora> From: Martin von Loewis To: issues@omg.org Subject: Python: Naming of POA classes User-Agent: SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) Emacs/20.4 (sparc-sun-solaris2.5.1) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII X-UIDL: 'ob!!8T$"!pGJ!!Y6Y!! [submitted by Duncan Grisby ] On page 13 (page 18 in 99-08-02), it says that module M results in a Python package M__POA containing the skeletons. In the next paragraph, it refers to the package POA_M. They can't both be right. In omniORBpy I use POA_M, since that is what the C++ mapping does. Regards, Martin X-Mailer: exmh version 2.0.2 2/24/98 To: Martin von Loewis cc: issues@omg.org Subject: Re: Python: Naming of POA classes In-reply-to: Your message of "Wed, 19 Jan 2000 16:21:35 +0100." <200001191521.QAA25715@pandora> Mime-Version: 1.0 Date: Thu, 20 Jan 2000 15:36:41 +1000 From: Keith Duddy Content-Type: text/plain; charset=us-ascii X-UIDL: &l&!!PM!e9fb[submitted by Duncan Grisby ] > >On page 13 (page 18 in 99-08-02), it says that module M results in a >Python package M__POA containing the skeletons. In the next paragraph, >it refers to the package POA_M. They can't both be right. In omniORBpy >I use POA_M, since that is what the C++ mapping does. Sounds fine to me Martin... K -- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Keith Duddy : dud at dstc.edu.au : http://www.dstc.edu.au/AU/staff/dud CRC for Enterprise Distributed Systems Technology (DSTC) General Purpose South, University of Queensland, 4072, Australia ph: +61 7 336 5 4310 :: fx: +61 7 336 5 4311 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2nd edition of my book ``Java Programming with CORBA'' now in bookshops >>> http://www.wiley.com/compbooks/vogel <<< ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Date: Fri, 24 Mar 2000 14:07:06 +0100 Message-Id: <200003241307.OAA03993@pandora> From: Martin von Loewis To: janssen@parc.xerox.com CC: python-ftf@omg.org In-reply-to: <00Mar23.165257pst."3686"@watson.parc.xerox.com> (message from Bill Janssen on Thu, 23 Mar 2000 16:53:00 PST) Subject: Issue 3237: Naming of POA classes References: <00Mar23.165257pst."3686"@watson.parc.xerox.com> User-Agent: SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) Emacs/20.6 (sparc-sun-solaris2.5.1) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII X-UIDL: %R""!';,!!AW&!!(jEe9 > > 3237: Naming of POA classes > > > > Correct example text: replace POA_M.I with POA__M.I > > > > Eeek! No, it's M__POA, not POA__M. It was specifically designed in > this fashion to allow the generated modules for M to sort together > lexicographically. Yes, in proposing a correction, I broke it in a different way. "M__POA.I" is the correct text. Regards, Martin Date: Fri, 24 Mar 2000 14:07:06 +0100 Message-Id: <200003241307.OAA03993@pandora> From: Martin von Loewis To: janssen@parc.xerox.com CC: python-ftf@omg.org In-reply-to: <00Mar23.165257pst."3686"@watson.parc.xerox.com> (message from Bill Janssen on Thu, 23 Mar 2000 16:53:00 PST) Subject: Issue 3237: Naming of POA classes References: <00Mar23.165257pst."3686"@watson.parc.xerox.com> User-Agent: SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) Emacs/20.6 (sparc-sun-solaris2.5.1) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII X-UIDL: %R""!';,!!AW&!!(jEe9 > > 3237: Naming of POA classes > > > > Correct example text: replace POA_M.I with POA__M.I > > > > Eeek! No, it's M__POA, not POA__M. It was specifically designed in > this fashion to allow the generated modules for M to sort together > lexicographically. Yes, in proposing a correction, I broke it in a different way. "M__POA.I" is the correct text. Regards, Martin To: Martin von Loewis cc: python-ftf@omg.org Subject: Re: Resolving issues In-Reply-To: Your message of "Thu, 23 Mar 2000 07:34:46 PST." <200003231533.QAA25641@pandora> From: Bill Janssen Message-Id: <00Mar23.165257pst."3686"@watson.parc.xerox.com> Date: Thu, 23 Mar 2000 16:53:00 PST Content-Type: text X-UIDL: @~g!!YD;e9eVNe9@Mf!! > 3237: Naming of POA classes > > Correct example text: replace POA_M.I with POA__M.I > Eeek! No, it's M__POA, not POA__M. It was specifically designed in this fashion to allow the generated modules for M to sort together lexicographically. Bill Date: Wed, 5 Apr 2000 07:43:48 -0400 (EDT) Message-Id: <200004051143.HAA11608@emerald.omg.org> To: Martin von Loewis , python-ftf@omg.org Subject: Issue 3237: Python: Naming of POA classes (python-ftf) From: "Jeffrey A. Marshall" X-Mailer: TWIG 2.1.1 Content-Type: text X-UIDL: 6m,!!R=V!!JE'!!>(kd9 I would like some clarification on the resolution of Issue 3237. I can understand what is supposed to happen in the following case: module M { interface I {}; }; --> M__POA.I is the skeleton generated but what happens with nested modules? module M { module Inner { interface I {}; }; }; --> M__POA.Inner__POA.I or --> M__POA.Inner.I # I assume this is right thanks, -jeff Date: Wed, 5 Apr 2000 18:29:59 +0200 Message-Id: <200004051629.SAA28788@pandora> From: Martin von Loewis To: jam@camros.com CC: python-ftf@omg.org In-reply-to: <200004051143.HAA11608@emerald.omg.org> (jam@camros.com) Subject: Re: Issue 3237: Python: Naming of POA classes (python-ftf) References: <200004051143.HAA11608@emerald.omg.org> Content-Type: text X-UIDL: &\d!!-;Ge9[M2e9`p$!! > but what happens with nested modules? > > module M { module Inner { interface I {}; }; }; > > --> M__POA.Inner__POA.I > > or > > --> M__POA.Inner.I # I assume this is right Indeed, the latter is right. This is expressed in the sentence # For the POA, the first qualifier of the fully-scoped name of the # interface is suffixed with "__POA". If you can propose a better wording to express that property (i.e. that the first part of the fully-qualified name is suffixed), please let me know, and I'll take this as an editorial change; provided the motion on issue 3237 passes as proposed. Regards, Martin To: Martin von Loewis cc: jam@camros.com, python-ftf@omg.org Subject: Re: Issue 3237: Python: Naming of POA classes (python-ftf) In-Reply-To: Your message of "Wed, 05 Apr 2000 09:30:23 PDT." <200004051629.SAA28788@pandora> From: Bill Janssen Message-Id: <00Apr5.112723pdt."3432"@watson.parc.xerox.com> Date: Wed, 5 Apr 2000 11:27:37 PDT Content-Type: text X-UIDL: =eK!!dP%e9*k$e9QQ/e9 > # For the POA, the first qualifier of the fully-scoped name of the > # interface is suffixed with "__POA". > > If you can propose a better wording to express that property > (i.e. that the first part of the fully-qualified name is suffixed), > please let me know, and I'll take this as an editorial change; > provided the motion on issue 3237 passes as proposed. Martin, I'd call it the first "element" of the fully-scoped name, rather than the first "qualifier". Bill To: Martin von Loewis cc: jam@camros.com, python-ftf@omg.org Subject: Re: Issue 3237: Python: Naming of POA classes (python-ftf) In-Reply-To: Your message of "Wed, 05 Apr 2000 09:30:23 PDT." <200004051629.SAA28788@pandora> From: Bill Janssen Message-Id: <00Apr5.112723pdt."3432"@watson.parc.xerox.com> Date: Wed, 5 Apr 2000 11:27:37 PDT Content-Type: text X-UIDL: =eK!!dP%e9*k$e9QQ/e9 > # For the POA, the first qualifier of the fully-scoped name of the > # interface is suffixed with "__POA". > > If you can propose a better wording to express that property > (i.e. that the first part of the fully-qualified name is suffixed), > please let me know, and I'll take this as an editorial change; > provided the motion on issue 3237 passes as proposed. Martin, I'd call it the first "element" of the fully-scoped name, rather than the first "qualifier". Bill