Issue 113: Contents of string literal exception identifier (c_mapping-rtf) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: Section 14.14 calls for a string literal which "uniquely identifies this exception type", but does not specify any rules for generating such identifiers. Resolution: Close with no change Revised Text: Actions taken: September 11, 1996: Received issue December 12, 1996: moved from cxx_revision to c-rev-wg October 5, 2000: closed issue Discussion: This does not seem to be an interoperability issue in that standard exceptions are defined and user exceptions have meaning only in the context of applications that understand both sides of the generation and reception of the exception. End of Annotations:===== From geoff Wed Sep 11 13:52:40 1996 Received: by amethyst.omg.org.omg.org (5.4R2.01/1.34) id AA05904; Wed, 11 Sep 1996 13:52:40 -0400 Date: Wed, 11 Sep 1996 13:52:40 -0400 From: geoff (Geoffrey Speare) Message-Id: <9609111752.AA05904@amethyst.omg.org.omg.org> To: issue-logger@omg.org Subject: C mapping: contents of string literal exception identifier? X-Omg-Issue: 113 Date: Mon, 9 Sep 1996 17:28:52 PDT Sender: Bill Janssen From: Bill Janssen To: issues@omg.org Subject: C mapping: contents of string literal exception identifier? Cc: orbos@omg.org Section 14.14 calls for a string literal which ``uniquely identifies this exception type'', but doesn't specify any rules for generating such identifiers. From this, I assume that every ORB implementation may use a different string for this purpose? Bill >From mail Thu Oct 31 13:17 EST 1996 Date: 31 Oct 96 09:58:59 -0800 From: "KCOLEMAN.US.ORACLE.COM" To: c-rev-wg@omg.org Subject: Comments on current C issues Content-Length: 4445 Some comments on the issues Bill has posted on his Web page: Issue 113 - Nature of exception identifiers --------- This is not an issue for the C mapping. For reasons of interoperability, the language mapping cannot mandate this. If you feel this should be nailed down, I think think this is an issue for the Orbos TF. I propose that the following C-RTF issues for discussion this week and next with a vote to be scheduled by 4/7/2000 if there is no significant issues raised before 3/31/2000. Issue 113: Contents of string literal exception identifier Summary: Section 14.14 calls for a string literal which "uniquely identifies this exception type", but does not specify any rules for generating such identifiers. Discussion: This does not seem to be an interoperability issue in that standard exceptions are defined and user exceptions have meaning only in the context of applications that understand both sides of the generation and reception of the exception. I propose that it be closed with no change