[omniORB] omniidl and C++ include guard naming

[Austin Bingham]

> > Is there any way to control the names that omniidl uses when generating 
> > include guards in C++ headers? If I'm dealing with two sets of IDL, both 
> > of which have a (for instance) Util.idl, the generated header files will 
> > both use the same macro definition for the include guard. Is there any way 
> > I can tell the C++ backend to use some sort of pre/suffix to differentiate 
> > these names? The problem, of course, is that these macros collide if some 
> > translation unit includes both of these generated headers. Thanks.
> 
> No, I'm afraid not. Can you just rename your IDL files to avoid
> confusion?

In this case I might be able to get away with it, but this problem seems 
untenable in the general case. I'd be happy to look into adding this 
functionality to the C++ backend, if others think it's reasonable. Should 
I perhaps take this up on the dev list?

Austin