This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: sstream
- To: Joe Buck <jbuck at possibly dot synopsys dot com>
- Subject: Re: sstream
- From: Benjamin Scherrey <scherrey at switchco dot com>
- Date: Mon, 21 Feb 2000 16:49:41 -0500
- CC: gcc <gcc at gcc dot gnu dot org>
- Organization: Proteus Technologies, Inc.
- References: <200002211718.JAA13098@possibly.synopsys.com>
- Reply-To: scherrey at proteus-tech dot com
I concur - v3 is nowhere near ready for prime time although the guys
are moving ahead diligently. Its a big friggin library with lots of
nuances. It would be real nice if a piecemeal integration of v3
components into v2 could be made but I dunno how deep and intrusive
the dependencies are - I fear this option is not practical. FWIW -
providing a stringstream as a stop gap measure for v2 would probably
be a fantastic benefit because use of strstream (and forgetting to
unfreeze stuff correctly) is one of the biggest source of memory leaks
that I find in people's C++ code and in every case a stringstream
would have prevented and was what the original code would have
preferred in the first place.
thanx & later,
Ben Scherrey
Joe Buck wrote:
>
> Martin writes:
> > I'd still like a comment on the original submission of that <sstream>
> > header. I think it should be integrated with the v2 libstdc++ -
> > whether or not this eventually appears in a release.
>
> I'd vote for putting it in, to benefit those who have an immediate need
> for it. v3 is not yet ready.