Re: [orbitcpp-list] orbitcpp-0.30 is out!

[Laszlo M. <las...@et...>]

>  > 2, On linux/ia32 (where I have a shared libstdc++) I get tons of
>  > warnings in the generated files using -Wall -W. Most (or all?) of them
>  > is about an unused parameter in the "operator new"s. It would be nice
>  > to see a fix for this in 0.30.1.
> Could you mail me the error please? I only get warnings from the C
> code generated by ORBit on my 32bit intel.

Well, I guess this is the relevant snippet from pass_xlate.cc:

   if(idlStruct.isVariableLength()) {
           m_header
           << endl
           << indent++ << "void* operator new(size_t size) {" << endl
           << indent << "return "
           << IDL_IMPL_C_NS "::"
           << idlStruct.getQualifiedCIdentifier() << "__alloc();" << endl;
           m_header
           << --indent << "};" << endl << endl;
           m_header
           << indent++ << "void operator delete(void* c_struct) {" << endl
           << indent <<  "::CORBA_free(c_struct);" << endl;
           m_header
           << --indent << "};" << endl << endl;

   }

In the generated "void* operator new(size_t size)" the "size" parameter
is not used, that's why I see warnings in the emitted code. Btw, for
clarity reasons I think op. new and delete could be explicitely defined
as "static". But this is just a syntactic sugar.

>  > 3, I'm not sure whether '#pragma inhibit push/pop' is supported, but it
>  > does not seems to work for me. I'm not sure whether it should work in
>  > the C binding either. Is it supported?
> Not yet, but you mentioning it has pushed it to the top of my TODO
> list :-)

Cool :) In the mean time I simply inserted some "#include"s into the
generated headers, and now I can compile my application. Wow!

Laszlo