stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance Diduck (JIRA)" <>
Subject [jira] Commented: (STDCXX-1) allow linking with other implementations
Date Tue, 27 Sep 2005 01:59:48 GMT
    [ ] 

Lance Diduck commented on STDCXX-1:

This is a paper I wrote a couple years ago at my last job outlining some of the more conceptual
reasons that motivate this issue

This problem is only getting worse -- for example, at my current job we routinely try to link
an "improved"  version of STLport, Xerces 2.5 and 2.6, log4cxx, some version of ACE, and a
couple of other things I've never heard of, all together in one huge makefile. Of course no
one thinks this is a good idea. But "changing the build" is out of the question -- and even
in a sane scenario, many vendors dictate the build options. 

Enabling all or portions of STDCXX code, to sit on top of whatever the current STL happens
to be, would be a huge deal. This would allow tons of developers to rely on STDCXX without
having to get everybody to coordinate on a single set of build options, or without having
to lobby an entire company (indeed the industry )  to do things your way. 

> allow linking with other implementations
> ----------------------------------------
>          Key: STDCXX-1
>          URL:
>      Project: STDCXX
>         Type: Improvement
>   Components: Configuration
>     Versions: 4.1.2
>  Environment: All.
>     Reporter: Martin Sebor

> This is an enhancement request to allow object files (libraries, or executable programs)
compiled against this implementation of the C++ Standard Library to link with others compiled
against another implementation (such as GNU libstdc++ or STLport).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message