Re: [DotGNU]Strategy for dealing with C++ virtual functions in a managed binding.

[James Michael DuPont]

--- Gopal V <address@hidden> wrote:
> If memory serves me right, Adam Treat wrote:
> > Our new strategy is then to call the libqt.so directly using
> mangled method 
> > names in our DllImport attributes.  
> 
> IMHO, this is a bad idea ... because eventhough g++ name mangling is 
> standardized, it's likely to change without much notice .. gcc 2.53
> had a switch, IIRC..

libiberty is what you want.
then you just link that in. gpled lib.

> 
> > The only way I can figure to handle this is to provide a C glue
> method 
> > for every virtual function in libqt :(  This is nasty and
> eliminates 
> 
> http://www.delorie.com/gnu/docs/gcc/gxxint_15.html
> 
> has the name mangling docs ... but I wouldn't like someone depending 
> on that for production code ....

Also this is the whole benefit of the new C++ Binary ABI.


> It's possible , because you already know the attributes of the
> classes
> in Qt , the names of classes and functions ... But my personal
> opinion
> is "It will always be a hack" .

Not with the introspector.

mike

=====
James Michael DuPont
http://introspector.sourceforge.net/

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com