Re: As promised, a few more questions

[Georg Seidel]
> For 2: I'm not quite sure about the status of this. You could say:
> "I don't mind, I'm only using gcc on linux", then you would not care.
> We, however, at the moment also support the microsoft visual c++
> compiler on win32. (Martin should know more details about name
> mangling...)

Name mangling is the smallest problem of c++ abi compatibility. There are
other issues like object layout, exception handling, stack layout ...

The compilers for non-windows platform converge atm against the [1] abi. 
On the windows platform most commercial compilers follow the visual c++ 
compiler. Otherwise it wouldn't be possible to use COM. The gcc in mingw 
and cygwin is problematic as it implements the [1] api. There were a lot 
of discussions about supporting the ms api but to my knowledge there 
isn't much progress (please correct me if i'm wrong).

The compilers for the Mac platform[2][3] are also changing to [1].

With the success of the new C++ abi industrial standard [1] the problems 
on the unix platforms will disappear. The gcc on the windows platform 
will stay problematic.


The other problem is the stl. There are a lot of incompatible stl
implementations and versions included with compilers. Using std::list or
std::string in the interface would render it quite impossible to mix
different compilers with their stdlibs.

Martin

[1]
http://www.codesourcery.com/cxx-abi/

[2] 
http://www.metrowerks.com/MW/Develop/Desktop/Macintosh/Professional/Mac9.htm

[3] 
http://developer.apple.com/documentation/DeveloperTools/gcc-3.3/gcc/index.html

_______________________________________________
gephex-devel mailing list
[email protected]
http://lists.gephex.org/mailman/listinfo/gephex-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBmiEaCm3i57PRsbsRAukCAJ4lgQkjjFeTZuOTc4B0rD5TXMl1QwCgrx4R
zV2yJZ/UNYvQYFfhzeGdI8g=
=r6vU
-----END PGP SIGNATURE-----