Issue 3702: tagged types mapped from abstract interfaces (ada-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: The current Ada mapping specifies that ada Abstract_Ref types mapped from IDL abstract interfaces should inherit directly from CORBA.AbstractBase.Ref, and not from CORBA.Object.Ref. It seems more natural to us to make Abstract_Ref types inherit from CORBA.Object.Ref. Otherwise, these Abstract_Ref tagged types would not inherit thr primitives of CORBA.Object.Ref (Is_A, Is_Equivalent, Hash) Resolution: Resolution: Close without change. The intended semantics for abstract interfaces are correctly reflected by inheriting from AbstractBase, rather than Object, as evidenced by the following section in the CORBA specification: “3. Abstract interfaces do not implicitly inherit from CORBA::Object. This is because they can represent either value types or CORBA object references, and value types do not necessarily support the object reference operations (see Section4.3, “Object Reference Operations,” on page4-8). If an IDL abstract interface type can be successfully narrowed to an object reference type (a regular IDL interface), then the CORBA::Object operations can be invoked on the narrowed object reference.” Disposition: Closed, no change Revised Text: Actions taken: June 13, 2000: received issue January 12, 2010: closed issue Discussion: End of Annotations:===== Date: Tue, 13 Jun 2000 11:26:58 -0400 (EDT) Message-Id: <200006131526.LAA21045@emerald.omg.org> From: fabien.azavant@adabroker.eu.org To: juergen@omg.org, web-incoming@omg.org Subject: Issue Report Content-Type: text X-UIDL: T)N!!Z5&!!*`He9=+Wd9 Name: Fabien Azavant Company: enst mailFrom: fabien.azavant@adabroker.eu.org Notification: Yes Specification: ada language mapping Section: 4.5.1 Formal #: Version: 1.2 Revision_Date: 05/04/2000 Page: Nature: Revision Severity: Minor full_desc: Specification: Ada Language Mapping Specification, v1.2, May 2000 Nature: Revision Severity: Minor Summary: tagged types mapped from abstract interfaces should inherit from CORBA.Object.Ref Description: The current Ada mapping specifies that ada Abstract_Ref types mapped from IDL abstract interfaces should inherit directly from CORBA.AbstractBase.Ref, and not from CORBA.Object.Ref. It seems more natural to us to make Abstract_Ref types inherit from CORBA.Object.Ref. Otherwise, these Abstract_Ref tagged types would not inherit thr primitives of CORBA.Object.Ref (Is_A, Is_Equivalent, Hash) To: ada-rtf@omg.org Cc: Nick Roberts Subject: Proposed resolution for 3702 From: Victor Giddings Date: Mon, 12 May 2008 09:10:07 -0400 X-Mailer: Apple Mail (2.753) Disposition: Closed, no change OMG Issue No: 3702 Title: Abstract Interfaces Should Inherit from CORBA.Object.Ref Source: École Nationale Supérieure des Télécommunications Fabien Azavant fabien.azavant@adabroker.eu.org Summary: The current Ada mapping specifies that ada Abstract_Ref types mapped from IDL abstract interfaces should inherit directly from CORBA.AbstractBase.Ref, and not from CORBA.Object.Ref. It seems more natural to us to make Abstract_Ref types inherit from CORBA.Object.Ref. Otherwise, these Abstract_Ref tagged types would not inherit the primitives of CORBA.Object.Ref (Is_A, Is_Equivalent, Hash) Resolution: Close without change. The intended semantics for abstract interfaces are correctly reflected by inheriting from AbstractBase, rather than Object, as evidenced by the following section in the CORBA specification: .3. Abstract interfaces do not implicitly inherit from CORBA::Object. This is because they can represent either value types or CORBA object references, and value types do not necessarily support the object reference operations (see Section4.3, .Object Reference Operations,. on page4-8). If an IDL abstract interface type can be successfully narrowed to an object reference type (a regular IDL interface), then the CORBA::Object operations can be invoked on the narrowed object reference.. Disposition: Closed, no change Victor Giddings Objective Interface Systems victor.giddings@mail.ois.com submit: Submit Issue Report