[omniORB] intermodule inheritance failure

[Renzo Tomaselli]

Thanks Duncan,
the same problem (inheritance from a typedef) appeared during early days of
3.0, but at that time it used to crash the back-end.
To anyone interested: the workaround is to insert a typedef referring to the
importing module which the back-end seems to forget about (while similar
typedefs are correctly generated for imported interfaces).
In my example the missing line was:

typedef DynLoader::_objref_TopObject _DynLoader__objref_TopObject;

Then it compiles fine. I will look forward to get 3.04.

Renzo

-----Original Message-----
From: Duncan Grisby <dgrisby@uk.research.att.com>
To: Renzo Tomaselli <renzo.tomaselli@tecnotp.it>
Cc: Omniorb list <omniorb-list@uk.research.att.com>
Date: giovedì 21 giugno 2001 13:38
Subject: Re: [omniORB] intermodule inheritance failure


>On Wednesday 20 June, "Renzo Tomaselli" wrote:
>
>>     I'm porting a fairly large environment from OmniORB 2.8 to 3.03 under
NT
>> 4.0, MSVC 6.0.
>> OmniORB binaries are those straight out of the box, while my IDL code is
>> generated automatically by Rational Rose.
>> I found a back-end problem when inheritance is used across modules, such
as:
>[...]
>
>I'm pretty certain this bug has already been fixed in CVS (although
>there's no entry on the bugs page for it). We're very close to doing a
>3.0.4 release, so it will be fixed in that.