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: "sebor at roguewave dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Dec 2005 16:27:17 -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 #15 from sebor at roguewave dot com 2005-12-08 16:27 -------
(In reply to comment #11)
Okay, I see your concern.
Well, IMO, your signatures are better than those required by the standard so if
you care about 100% compliance you (or Paolo -- and I promise not to beat him
;-) should open an issue with the LWG and try to get the standard changed. I
will support the change. Until the LWG issue is resolved (and hopefully even
after that) you can leave your signatures alone.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25304