Bug#236912: [Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-09 Thread Phil Edwards
On Tue, Mar 09, 2004 at 07:32:32PM +0100, Jeroen T. Vermeulen wrote: > On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote: > > > > More to the point, it doesn't matter how it's implemented, and the user > > > should not care. It only matters that > > > > > > std::bad_alloc foo; >

Bug#236912: [Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-09 Thread Jeroen T. Vermeulen
On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote: > > More to the point, it doesn't matter how it's implemented, and the user > > should not care. It only matters that > > > > std::bad_alloc foo; > > std::cerr << foo.what() << std::endl; > > > > works, which the submitter

Bug#236912: [Bug libstdc++/14493] No std::bad_alloc::what() const

2004-03-08 Thread Matthias Klose
[resending for the inclusion to the Debian BTS] Phil Edwards writes: > close 236912 > thanks > > This bug report reinforces my opinion that bug reports consisting of > claims of nonconformance, but not accompanied by a testcase, should be > immediately closed. > > > On Mon, Mar 08, 2004 at 11:1