Issues for Ada 2003 Revision Task Force

To comment on any of these issues, send email to ada-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 3639: The Ada mapping of the Interface Repository.
Issue 6344: Ada Mapping of Sequences Too Heavy

Issue 3639: The Ada mapping of the Interface Repository. (ada-rtf)

Click here for this issue's archive.
Nature: Revision
Severity: Significant
Summary:

Summary: Standardisation of the declaration of the Ada units mapping the
        Interface Repository Specification

Description:
	The mapping of the IDL specification of the IR in Ada implies
	the creation of forward declarations of interfaces (the
	"IDLType" interface for instance). Those should be mapped in
	Ada to subpackages of CORBA using the CORBA.Forward
	package. This leads to a circular dependency in the new CORBA
	package.

Proposed solution:
        These interfaces cannot be mapped as instanciations of
        CORBA.Forward that are child packages of CORBA, because
        they are subsequently used in the definition of record
        types in the declaration of CORBA (eg interface IDLType
        as a component of StructMember).

	We therefore propose the following addition to the standard
        mapping definition for module CORBA:

        "The types defined within module CORBA by the Interface
        Repository Specification (formal/99-10-07, p10-56 to 10-68),
        except the TypeCode and ORB interfaces, shall be mapped to a
        (child) library package CORBA.Repository_Root." 

	A comment at the end of the declaration of the package CORBA
	implies that this is probably the intent of the author to
	provide such a standard child unit. 

	We further propose that the contents of the declaration of
	child package CORBA.Repository_Root be standardized. We will
	provide a proposed specification on request.

Resolution:
Revised Text:
Actions taken:
May 23, 2000: received issue

Discussion:

These interfaces cannot be mapped as instanciations of CORBA.Forward that
are child packages of CORBA, because they are subsequently used in the
definition of record types in the declaration of CORBA (eg interface IDLType as a
component of StructMember).
We therefore propose the following addition to the standard mapping definition
for module CORBA:
"The types defined within module CORBA by the Interface Repository
Specification (formal/99-10-07, p10-56 to 10-68), except the TypeCode and ORB
interfaces, shall be mapped to a (child) library package
CORBA.Repository_Root."
A comment at the end of the declaration of the package CORBA implies that this
is probably the intent of the author to provide such a standard child unit.
We further propose that the contents of the declaration of child package
CORBA.Repository_Root be standardized. We will provide a proposed
specification on request.
Discussion:
Deferred due to lack of time.
Disposition: Deferred

Issue 6344: Ada Mapping of Sequences Too Heavy (ada-rtf)

Click here for this issue's archive.
Source: Objective Interface Systems (Mr. Victor Giddings, victor.giddings(at)mail.ois.com)
Nature: Uncategorized Issue
Severity:
Summary:

The current mapping of IDL sequences to the Ada language results in a instantiation of a defined generic package. However, each instantiation results in roughly 150K of additional object code. This is excessive for embedded systems, especially if multiple sequences are used in an application. A lightweight alternative, such as the mapping defined for C++, should be defined.

Resolution:
Revised Text:
Actions taken:
October 21, 2003: received issue

Discussion:

Deferred due to lack of time.
Disposition: Deferred