Re: stringstream strange output
On Sep 24, 11:37 am, drusakov <dmitry.rusa...@googlemail.com> wrote:
we write one very high-performance application and stlport was
one of the things recommended by other people (including other
group here, at our workplace) to boost its performance.
Compared to what? In the past, a number of people have
recommended STL port, mostly, I suspect, because it was GPL, and
they believed in GPL, but partially, perhaps, because many
library implementations were of bad quality. With Sun CC, even
today, you have a choice between Rogue Wave and STL Port: with
the versions delivered with Sun CC, the quality of both is
pretty bad, and the Rogue Wave library also has some very
serious performance problems---if you have a high-performance
application and are compiling with Sun CC, you probably should
use STL port. Otherwise, however, I don't think so.
I actually beleive the 'bug' is a less of stlport bug, but
rather something in the way we compile and build the project,
like order of linked libraries etc.
I don't think so. I made a quick test, and got exactly the same
symptoms with Sun CC. So it's almost certainly an error in the
library.
I'm not very heavy into this stuff, so it is all rather
guessing, our typical compilation line looks like: g++ -O3
-Wall -Woverloaded-virtual - Wpointer-arith -Wwrite-strings
-fomit-frame-pointer -pipe -fexceptions -fpic -D_PTHREADS
-D_REENTRANT.
As we reverted the changes back yesterday late night and given
the (permanent) time pressures, it is now impractical to
recreate the exact conditions again to investigate. Just want
to see if someone on the net came across something similar and
can pin point the cause.
James - interesting opinion re stlport. We were under
impression that everyone recommends it for performance
improvement.
It's recommended for performance improvement if you are using
Sun CC; file IO, in particular, is significantly faster.
Otherwise, no. The quality is not very good, at least not in
the version which comes with Sun CC. If you're using g++, just
use the library that comes with it.
That's good advice in general, and always has been. Unless
there is a very strong reason for doing otherwise, stick with
the library which came with your compiler.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34