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

[David Morgenlender]

David,

>The IDL compiler treats #includes in a special way because it assumes =
that
>what you are including will be IDL, and also that you will compile this
>IDL separately.
>
>If you want #includes to work the way you expect them to then you could
>try running the C pre-processor over your IDL file separately. You will
>then need to remove the information that the C pre-processor adds before
>running it through the IDL compiler. The C pre-processor adds lines that
>start with a # and contain info about what file and line number it is
>currently at.
>
>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!
>
>I hope this solution works for you.

Thanks for the suggestion.  That sounds like it should work.  But it will=
 take
more time than I have to spend on it now.  So for now I'm going to use =
the
kludge of treating the struct as an array of bytes as far as CORBA is =
concerned.
I'll write some low level code to hide this from the app, which will only=
 deal
with the struct.

=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