This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/25304] std::fill_n, std::generate_n incorrect signature
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Dec 2005 00:20:00 -0000
- Subject: [Bug libstdc++/25304] std::fill_n, std::generate_n incorrect signature
- References: <bug-25304-1186@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from pcarlini at suse dot de 2005-12-08 00:20 -------
(In reply to comment #7)
> FWIW, I think Andrew makes a good point in comment #1. The algorithms really
> should return the iterator, otherwise the caller may not be able to find out
> the state of the iterator after the algorithm returns (e.g., when the iterator
> is ostreambuf_iterator).
Ah, I see. Then the issue is more subtle than uninitialized_fill_n in 16505...
> It may not be a bad idea to open an issue (or at least
> bring it up on the reflector).
Ok, I will, if you don't beat me ;)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25304