[omniORB] #include in .IDL file works incorrectly!!!

[David Morgenlender]

Rusty,
=20
>> The advantage of this approach is that the IDL compiler will see a =
single
>> pure IDL file, and will define your structure in C++ for you. All you =
have
>> to do is write a script to automate it!
>>=20
>
>and it can be done automatically in the makefile (you ARE using
>make files, right?).  If I were doing it, I'd run the c preprocessor
>on a file, do some diffs, and make a sed or awk or grep or perl=20
>script to remove the new stuff added to the file, then stick that
>into the makefile...

I'm only using makefiles indirectly.  I'm using the Visual C++ 5 IDE.  So=
 I'd
have to figure out how to customize the build in the IDE to do this;  but=
 I
believe that is readily doable.

However, I don't have time to deal with this approach now, especially =
writing
the script (& having to learn awk, or whatever).  So I'm going to take =
the Q&D
approach of treating the struct as an array of bytes at the low level & =
for
CORBA.  The higher level app code will still deal with it as a struct.

Thanks for the suggestion.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D