This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: cerr and NULL terminates program + string::find() weird results

From: Benjamin Kosnik <bkoz at redhat dot com>
To: libstdc++ at gcc dot gnu dot org
Date: Wed, 16 Oct 2002 20:33:41 -0500
Subject: Re: cerr and NULL terminates program + string::find() weird results
Organization: Red Hat / Chicago
References: <002d01c2720c$1f571550$1201a8c0@jaucho><m3y993v6mb.fsf@soliton.integrable-solutions.net><00d401c2750c$caf5d100$17005d0a@ottawa><m3y98yh857.fsf@soliton.integrable-solutions.net><017901c2755d$038a0360$6401a8c0@SOLE><20021016204727.A24722@disaster.jaj.com>

This problem was discussed last year. It was determined that, on
balance, setting badbit is the most consistent way of dealing with null
pointer errors in for output (specified in other inserters, like streambuf*). 

I stand by that decision. I think it's wise.

See:
27.6.2.5.3 - basic_ostream::operator<< [lib.ostream.inserters]


-benjamin

References:
- cerr and NULL terminates program + string::find() weird results
  - From: Anibal Jodorcovsky
- Re: cerr and NULL terminates program + string::find() weird results
  - From: Gabriel Dos Reis
- Re: cerr and NULL terminates program + string::find() weird results
  - From: Anibal Jodorcovsky
- Re: cerr and NULL terminates program + string::find() weird results
  - From: Gabriel Dos Reis
- Re: cerr and NULL terminates program + string::find() weird results
  - From: Anibal Jodorcovsky
- Re: cerr and NULL terminates program + string::find() weird results
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]