This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: serious bug in libstdc++-3.2 std::copy?

From: Phil Edwards <phil at jaj dot com>
To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
Cc: "Neal D. Becker" <nbecker at hns dot com>, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
Date: Wed, 4 Dec 2002 14:34:43 -0500
Subject: Re: serious bug in libstdc++-3.2 std::copy?
References: <x884r9tycmn.fsf@rpppc1.md.hns.com> <m3u1htr6g2.fsf@uniton.integrable-solutions.net>

On Wed, Dec 04, 2002 at 07:21:17PM +0100, Gabriel Dos Reis wrote:
> If step 4 is OK, then step 5 ought to be OK: the input iterator is of
> pointer type. 
> 
> As an aside,  this is a case where I really do prefer class
> template-based compile-time dispatcher over overloading.

Seconded.  Neal, you might try defining _GLIBCPP_CONCEPT_CHECKS while
compiling and see if any additional warnings appear.


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

References:
- serious bug in libstdc++-3.2 std::copy?
  - From: Neal D. Becker
- Re: serious bug in libstdc++-3.2 std::copy?
  - From: Gabriel Dos Reis

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