Dan Kegel wrote:
Kay Ramme - Sun Germany - Hamburg wrote:
The core is already 'C' based. Please see my other posting.
Your other post made it clear that the core is C++
internally, but exports only pure C functions to the world. Right?
That's not quite 'C' based, because of the symbol versioning
problems you're well aware of, so you need to make a stronger
statement here (like
"It's C++ based, but all global symbols
it exports or imports (even the internal ones used by the C++
compiler and libstdc++) are pure C,
and we absolutely, positively promise that you can use this
C interface to link to your C++ app, no matter what version of
C++ you used to compile your app in").
Can you make such a promise?
It turned out to work quite well in the past, but there is too much
unknown/unexplored territory here to be confident with any strong
promise, I fear...
[...]
> Unfortunately it is not necessarily true,
> that libraries compiled with different (in terms of ABI)
> C++ compilers can be used in the same process, because of symbol
conflicts.
Although maybe having URE link against libstdc++.a would
remove this part of the problem.
(http://gcc.gnu.org/PR21405 talks about this issue a bit with
regards to STL inlines.)
Note that OOo uses STLport on top of libstdc++, so that OOo's
dependencies on libstdc++ are not that large.
-Stephan
Cheers,
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
