Issue 542: Interface Repository (orb_revision) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: In the Interface Repository spec, StructDef,UnionDef, and ExceptionDef should be derived from Container,since types can be defined within structs,unions,and exceptions according to IDL gram Resolution: resolved, close issue Revised Text: In section 6.5.10 add a sentence to the end of the first paragraph:"It can contain structs, unions, and enums." and change the IDL declaration (see corresponding archive file) Actions taken: April 15, 1997: received issue June 20, 1997: closed issue Discussion: End of Annotations:===== Return-Path: X-Sender: vinoski@karloff.boston.iona.ie Date: Tue, 15 Apr 1997 13:17:51 -0400 From: Steve Vinoski Subject: Core issue: Interface Repository Errors-To: owner-issues Sender: owner-issues X-OMG: issues To: issues In the Interface Repository specification, StructDef, UnionDef, and ExceptionDef should all also be derived from Container, since types can be defined within structs, unions, and exceptions according to the IDL grammar. --steve Return-Path: X-Sender: rabin@postman.opengroup.org Date: Wed, 4 Jun 1997 12:12:09 -0400 To: "Russell L. Newcombe" From: Paul Rabin Subject: Re: correction to resolution of Core RTF issue 542 Cc: orb_revision@omg.org, Mark Coats Russ, You asked whether it is possible to correct items 10, 11, and 12 in the list of changes to the proposed Core RTF Final Report, changing each of the three occurances of: > "It can contain constants, typedefs, and exceptions." > > to: > > "It can contain structs, unions, and enums." It's possible. Do any Core RTF members object to this correction? Paul Paul Rabin tel: +1 617 621 8873 The Open Group - Open Software Foundation fax: +1 617 621 0584 11 Cambridge Center email: p.rabin@opengroup.org Cambridge, MA 02142-1405 USA #542 CLOSED Comment: In the Interface Repository spec, StructDef,UnionDef, and ExceptionDef should be derived from Container,since types can be defined within structs,unions,and exceptions according to the IDL grammar. Resolution: In section 6.5.10 add a sentence to the end of the first paragraph: "It can contain structs, unions, and enums." and change the IDL declaration from: interface StructDef:TypedefDef { to: interface StructDef:TypedefDef, Container { In section 6.5.11 add a sentence to the end of the first paragraph: "It can contain structs, unions, and enums." and change the IDL declaration from: interface UnionDef:TypedefDef { to: interface UnionDef:TypedefDef, Container { In section 6.5.19 add a sentence to the end of the first paragraph: "It can contain structs, unions, and enums." Change the IDL declaration from: interface ExceptionDef:Contained { to: interface ExceptionDef:Contained, Container { In 6.8, change the IDL declarations of the three interfaces StructDef, UnionDef, and ExceptionDef so they inherit from Container: interface StructDef:TypedefDef, Container { interface UnionDef:TypedefDef, Container { interface ExceptionDef:Contained, Container { Return-Path: From: Martin Chapman Date: Thu, 21 Aug 1997 12:18:36 +0100 To: Paul Rabin CC: orb_revision@omg.org Subject: [tcross@iona.com: IFR issues at OMG] Paul, As promised at a conf call a few weeks ago, we have looked at the currently logged IFR issues. Terence Cross trawled through them and here is his response (marked TC>). Terence can be available for a core rtf conf call to try and resolve these. Let us know when its on the agenda. Martin. ---- Report on open IFR issues at OMG 2.1 task force ----------------------------------------------- General ------- A call needs to be made as to whether or not IDL definned exceptions should be included in the IFR module. It would be quite a large change but would be more in-line with other services to add IFR specific exceptions. Also I had thought that I raised an issue about repository IDs, that the default format would include a null prefix followed by a slash. I dont see it there can I raise it now? Also another issue is that I cant see any operations that allow for the creation of ExceptionDef objects. I would expect the following within interface Container: ExceptionDef create_exception ( in RepositoryId id, in Identifier name, in VersionSpec version, in StructMemberSeq members ); Issue 542: Interface Repository Source: IONA (Mr. Steve Vinoski, vinoski@iona.com) Nature: Uncategorized Severity: Summary: In the Interface Repository spec, StructDef,UnionDef, and ExceptionDef should be derived from Container,since types can be defined within structs,unions,and exceptions according to IDL gram Resolution: In section 6.5.10 add a sentence to the end of the first paragraph:"It can contain structs, unions, and enums." and change the IDL declaration (see corresponding archive file) Actions taken: 04/15/1997: received issue 06/20/1997: closed issue TC> I think that the IDL grammar should simplified so that TC> included these things in such structured types is depracated.