public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109922] <iomanip>: consider removing operator>> for istream >> setfill(c)
Date: Thu, 25 May 2023 09:56:52 +0000 [thread overview]
Message-ID: <bug-109922-4-ecqURvE0Xf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109922-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109922
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> I don't think the 27-652 change from N0958 was applied to the draft, but
It wasn't applied verbatim, because the proposed resolution only talked about
basic_ostream. The final change applied to the draft was corrected to refer to
both basic_ostream and basic_istream.
> 27-651 in https://www.open-std.org/jtc1/sc22/wg21/docs/papers/1996/N0964.pdf
> changed setfill.
I wonder if this was just an editing conflict, and the change for 27-651 should
actually have included basic_istream, as the change for 27-652 did.
Either way, it's not in the standard now and has no useful purpose, so I think
we should deprecate it for GCC 14 and remove it in a future release.
next prev parent reply other threads:[~2023-05-25 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 10:16 [Bug libstdc++/109922] New: " fsb4000 at yandex dot ru
2023-05-22 13:27 ` [Bug libstdc++/109922] " redi at gcc dot gnu.org
2023-05-23 2:12 ` de34 at live dot cn
2023-05-23 2:22 ` de34 at live dot cn
2023-05-25 9:24 ` redi at gcc dot gnu.org
2023-05-25 9:56 ` redi at gcc dot gnu.org [this message]
2023-05-31 12:21 ` cvs-commit at gcc dot gnu.org
2023-05-31 12:24 ` redi at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-109922-4-ecqURvE0Xf@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).