[omniORB] Strange code produced by omniidl2
David.Chung@USPTO.GOV
David.Chung@USPTO.GOV
Thu, 8 Jul 1999 09:05:24 -0400
Ok, let me give one more crack at it.
When things are forward declared,
their definition, I think, must be given later in the code.
In your IDL files, I do not see
the definition of the forward declared interface "bs". Could this
be the problem? Have you already tried defining it to see if it makes any
difference?
> -----Original Message-----
> From: ncb@adaptivebroadband.com [SMTP:ncb@adaptivebroadband.com]
> Sent: Thursday, July 08, 1999 5:25 AM
> To: Chung, David
> Cc: ncb@adaptivebroadband.com; omniorb-list@uk.research.att.com
> Subject: Re: [omniORB] Strange code produced by omniidl2
>
> David.Chung@USPTO.GOV wrote:
> >
> > My earlier e-mail made embarassing statements -- I must have
> been
> > qute confused.
> >
> > IDL doesnot permit forward declarations for anything except
> > interfaces.
> > As it stands, you are trying to forward declare bs module. So, it won't
> > compile.
> > [see, p. 74 of "Advanced CORBA Programming with C++", by Henning and
> > Vinoski].
> >
>
> yeah, but I AM forward declaring an interface. It just happens to be in
> a module (the declaration syntax for declaring an interface within a
> module is
> module xxx {
> interface yyy;
> };
> from p.102 of my copy of the same book (probably later edition)).
>
> Anyway, the IDL DOES compile to code, it just creates dodgy code in this
> case (IMO).
>
> Nick