[omniORB] TRUE, FALSE, and long

[Bjørn Wennberg]

David Riddoch <djr@uk.research.att.com> writes:

> On Wed, 26 May 1999, Laurent Pointal wrote:
> 
> > [omniORB2.7.1, NT4SP1]
> > 
> > Hello,
> > 
> > I recently make the following error in one of my IDL files:
> > 
> > 	const long MY_VALUE	= FALSE ;
> > 
> > omniidl2 has no problem with that, but when I use another IDL compiler, I
> > get an error about incompatible types... posting in the list of the other
> > ORB, it seems that TRUE/FALSE are values for a boolean, not for a long (as
> > they can be used in C/C++). Can omniidl2 be modified to refuse boolean
> > values for long types?
> 
> Sorry, but I don't think this is worth the effort at the moment. Lots of
> more important things to fix/improve/implement!
> 

I'm guessing that this is happening under ms-win, right? Aren't there any
pragmas you can define to avoid these warnings, since warnings are all 
they are?

> > As I deal with problem of bool values, I have a recurent warning from
> > omniorb sources:
> > 
> > Q:\omniorb_2.7.1\include\omniORB2/bufferedStream.h(621) : warning C4800:
> > 'unsigned char' : forcing value to bool 'true' or 'false' (performance
> > warning)
> > 
[snip]

-- 
-------------------------------------------------------
Bjørn Wennberg       email: bjornw@colargol.idb.hist.no 
                        ms: +47 959 92 657