
| Key: |
STDCXX-1
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Martin Sebor
|
| Votes: |
1
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
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).
|
|
Description
|
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). |
Show » |
|
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.