Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199911171803.MAA07439@pluto.xraylith.wisc.edu>
To:	"Singer, Robert (AZ76)" <RSinger AT space DOT honeywell DOT com>
cc:	John Chang <jbum AT post DOT com>, cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: sstream header file
In-Reply-To:	Your message of "Wed, 17 Nov 1999 09:03:55 MST."
	<EDB6CC8E1E50D2119F2700A0C9B578FA4CE9A8 AT az76ms02 DOT az76 DOT honeywell DOT com>
Date:	Wed, 17 Nov 1999 12:03:00 -0600
From:	Mumit Khan <khan AT nanotech DOT wisc DOT edu>

"Singer, Robert (AZ76)" <RSinger AT space DOT honeywell DOT com> writes:
> What about strstream? It has istrstream and ostrstream and they have been
> working fine for me as string streams. There are some differences between
> GCC & MSVC++ implementations...

ststream is deprecated, which means new code shouldn't be using it, and
should use string streams instead (strstreams has some problems where
you can end up with dangling pointers unless you take care to freeze
and unfreeze the internal buffer correctly).

Unfortunately, GNU C++ library doesn't come with string streams yet.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -