I would prefer not to touch to the new names now that boost supports
it even if it is still in beta.
I realized that heterogeneous naming convention was a real pain for
multi platform build systems like the one used by boost. So I decided to
make windows' ones closer to unix one as I concider that unix names was
clearer. The only difference is that gcc 'g' debug suffix became 'd' and
there is no symbolic link under windows OS so the only library name is
the one with major and minor version number.
I do not think that STLport lib names are worst than Microsoft ones,
msvcrt or msvcrtd is not really obvious, no ! Moreover when you see
names from other company, Roguewave for instance, STLport libs are
Michael Fink wrote:
>the library names were changed recently and now contain the STLport
>version, and I think that's ok for me (it's what boost does, too).
>Although the names are a bit hard to read. Here's the list of files after
>build in the "bin" folder:
>I think the debug and stldebug versions are a bit hard to read. couldn't
>we insert some underline char "_" or dash "-" to separate the lib and app
>name from the version? IMHO it would be much more readable and a bit more
>convenient for developers.
>SF.Net email is sponsored by:
>Tame your development challenges with Apache's Geronimo App Server. Download
>it for free - -and be entered to win a 42" plasma tv or your very own
>Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
>Stlport-devel mailing list