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
Package: libstdc++5-3.3-dev
Version: 1:3.3.3-2
Severity: minor
File: /usr/include/c++/3.3/new
std::bad_alloc doesn't seem to define a what() (std par. 18.4.2.1)
leading to unintelligible error messages.
-- System Information:
Debian Release: testing/unstable
Architecture: powerpc (ppc)
Kernel: Li
Package: g++-3.3
Version: 1:3.3.3-0pre2
Severity: minor
In this example the error message mentions the wrong namespace:
namespace outer { namespace inner { void foo(); } }
void outer::foo()
{
// error: `void outer::foo()' should have been declared inside `outer'
}
-- System Information:
Debia
On Sun, Jun 01, 2003 at 04:28:40PM +0200, Matthias Klose wrote:
>
> Jeroen, please can you provide the preprocessed sources?
>From what I can reconstruct now, it's just a matter of what a combination of
conflicting options (-Wmissing-noreturn and -ansi) should mean. Never mind;
please close the
Package: g++-3.2
Version: 1:3.2.2-0pre8
Severity: wishlist
Tags: upstream
Even in ANSI mode (in my case, using -pedantic) the compiler suggests
function attrbiutes, e.g.:
warning: function might be possible candidate for attribute
`noreturn'
This seems appropriate only when compiling without
Package: libstdc++2.10-dev
Version: 1:2.95.4-9
Severity: normal
File: /usr/include/g++-3/multimap.h
Tags: patch
AFAICS this problem is still around in the latest versions that come
with g++-3.1. The obsolete still exists, but the more
current equivalent does not.
For a quick fix, create a new
6 matches
Mail list logo
