Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!brunix!sdm
From: sdm@cs.brown.edu (Scott Meyers)
Newsgroups: comp.lang.c++
Subject: iostream char* constructors
Message-ID: <44815@brunix.UUCP>
Date: 12 Jul 90 03:59:48 GMT
Sender: news@brunix.UUCP
Reply-To: sdm@cs.brown.edu (Scott Meyers)
Organization: Brown University Department of Computer Science
Lines: 9

The public constructors for istrstream (AT&T release 2.0) take char*
arguments, not const char* const, as I expected.  Is this an oversight, or
is it really the case that if I initialize an istrstream with a string, the
string may be modified as I read from the istrstream?  

This seeming discrepancy between char* and const char* const isn't limited
to istrstreams -- it occurs elsewhere in the iostream library as well.

Scott