Issue 3074: Problem with AbstractBase definition (cxx_revision)
Source: Floorboard Software (Mr. Jonathan Biggar, jon(at)floorboard.com)
Nature: Uncategorized Issue
Severity: 
Summary: In the CORBA 2.3 spec, section 6.2, CORBA::AbstractBase is defined as:

module CORBA {
    native AbstractBase;
};

This implies that the C++ mapping for AbstractBase when used as a
parameter is like this:

class DataOutputStream { // from CORBA 2.3, section 5.5.2
    void write_Abstract(AbstractBase value);
};

But section 1.18.1 of the CORBA 2.3 C++ mapping makes it clear that the
signature should be:

class DataOutputStream { // 
    void write_Abstract(AbstractBase_ptr value);
};

Now I know that DataInputStream & DataOutputStream can be special cased
to handle this, but if we need to add additional operations that use
AbstractBase in the future, it would be nice if this could be fixed to
behave consistently with the other native type mappings to C++.

Resolution: 
Revised Text: 
Actions taken:
December 2, 1999: received issue
December 7, 1999: moved from Core to C++ RTF
Discussion: 
deferred in June 2011 to the next RTF
End of Annotations:=====
Sender: jbiggar@cisco.com
Message-ID: <3846EDEC.79C7E289@floorboard.com>
Date: Thu, 02 Dec 1999 14:08:44 -0800
From: Jonathan Biggar <jon@floorboard.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: issues@omg.org, cxx_revision@omg.org
Subject: Problem with AbstractBase definition
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: c"V!!E)pd9<Uad9?*$e9

In the CORBA 2.3 spec, section 6.2, CORBA::AbstractBase is defined as:

module CORBA {
    native AbstractBase;
};

This implies that the C++ mapping for AbstractBase when used as a
parameter is like this:

class DataOutputStream { // from CORBA 2.3, section 5.5.2
    void write_Abstract(AbstractBase value);
};

But section 1.18.1 of the CORBA 2.3 C++ mapping makes it clear that
the
signature should be:

class DataOutputStream { // 
    void write_Abstract(AbstractBase_ptr value);
};

Now I know that DataInputStream & DataOutputStream can be special
cased
to handle this, but if we need to add additional operations that use
AbstractBase in the future, it would be nice if this could be fixed to
behave consistently with the other native type mappings to C++.

-- 
Jon Biggar
Floorboard Software
jon@floorboard.com
jon@biggar.org
Sender: jon@floorboard.com
Message-ID: <384C65FD.ACC5337A@floorboard.com>
Date: Mon, 06 Dec 1999 17:42:21 -0800
From: Jonathan Biggar <jon@floorboard.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.5.1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: Jishnu Mukerji <jis@fpk.hp.com>
CC: Juergen Boldt <juergen@omg.org>, issues@emerald.omg.org,
        orb_revision@emerald.omg.org
Subject: Re: issue 3074 -- Core RTF Issue
References: <4.1.19991206154638.009b5c30@emerald.omg.org>
<384C316F.DC1129AF@fpk.hp.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: Edf!!'kZd9<A!e9&g1!!

Jishnu Mukerji wrote:
> 
> That one is a C++ RTF issue, not a Core RTF issue. Nothing can be
> done
> in the core to fix this.:-)

Actually, something could be done in the Core, but since we apparently
have developed a philosophy of not making core changes in order to fix
problems with a single language mapping unless there is no other way,
I
didn't call this one a core problem.

What could be done in the core would be to make AbstractBase a
keyword,
just like ValueBase and Object.

-- 
Jon Biggar
Floorboard Software
jon@floorboard.com
jon@biggar.org