>>>>> "Garrett Rooney" <rooneg@electricjellyfish.net>:
> It is certainly a problem of similar scope, although not exposing
> stuff like the STL probably also means not using it internally,
> since it's kind of tricky to require the linking in of multiple STL
> implementations if we use one and the app using our libraries uses
> another. Not saying it's impossible, just hard.
Granted linking with multiple "STL" implementations is a pain. But
why would you want to use multiple implementations of
that-subset-of-the-standard-C++-library-colloqually-known-as-"STL"
these days?
The native standard libraries of MSVC7 and g++3 and 4 (including mingw
and cygwin). are good enough to use, and have been so for quite a
while. (are there any other C++ compilers that are important these
days? SunPRO? Intel? If so, I'm guessing they have quite adequate
standard C++ libraries)
<unsolicited-lurker-advice>
On the note of the subject of this thread: stay with C unless you have
_really_ compelling reasons to change it. And if you have to change
it, change it to something in the mainstream.
</unsolicited-lurker-advice>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 22 20:03:57 2006