[omniORB] Warnings from omniORB header files

Mike Richmond mike.richmond at globalgraphics.com
Tue Jan 26 10:36:04 GMT 2010


On 25 Jan 2010, at 17:22, Duncan Grisby wrote:

> On Mon, 2010-01-25 at 16:53 +0000, Mike Richmond wrote:
>
>> I see the following warnings when compiling against the omniORB 4.1.4
>> headers with Visual C++ 8 options "-W4 -Wp64".  C4512 is from -W4,
>> the others are from -Wp64.  I'm happy to squash them at the moment
>> with #pragma warning, but it would be nice if they could be addressed
>> in a future version.
>>
>> ...\omniORB_4.1.4\include\omniORB4/stringtypes.h(149) : warning
>> C4267 : 'argument' : conversion from 'size_t' to 'int', possible loss
>> of data
>
> -Wp64 is warning about potential 64 bit issues. What it's not taking
> into account is that when omniORB is compiled on a 64 bit platform, a
> whole load of the types are defined differently. This particular  
> warning
> isn't actually covered by that, but the vast majority of them are.  
> It's
> definitely not possible to construct the headers to be free from
> warnings of that kind.

Fair enough.


>> ...\omniORB_4.1.4\include\omniORB4/stringtypes.h(583) : warning
>> C4512 : '_CORBA_String_inout' : assignment operator could not be
>> generated
>
> I don't know why the compiler thinks it can't generate an assignment
> operatoe here. Does it remove the warning if you define a do-nothing
> assignment operator there?

Yes.  Adding:

   inline _CORBA_String_inout & operator = (const _CORBA_String_inout  
&) { return *this; }

removes the warning.


Mike




More information about the omniORB-list mailing list