[omniORB] Header file conflicts in OS X.

[Toby Smith]

Hi,

I have an annoying problem when using omniORB in Mac OS X development
environments.

Thanks to some sketchy parameter naming choices in a few of the omniORB
header files, coupled with Apple defining nil to be 0 in some of its
system header files, it's common to run into grief when trying to include
both Apple and omniORB headers.  For an example of this in action, try to
compile a file that does:

#include <CoreFoundation/CFString.h>
#include <omniORB4/CORBA.h>


It looks like someone used a better parameter name, "is_nil," in a few
places in the headers, but there's still enough bare "nil" usages that
there's trouble.  In the 4.0.5 build, here's where the nils are:

omniORB4/CORBA_Current.h:63
omniORB4/CORBA_BOA.h:97-98
omniORB4/CORBA_ORB.h:263-264
omniORB4/poa.h:602-603
omniORB4/internal/corbaBoa.h:72
omniORB4/internal/corbaOrb.h:73
omniORB4/internal/objectAdapter.h:248

Changing the instances of 'nil' on those lines to 'is_nil' will make the
world a much happier place.

Regards,
tob