From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Document istreambuf_iterator base class change [PR 92285]
Date: Wed, 4 Nov 2020 12:59:50 +0000 [thread overview]
Message-ID: <20201104125950.GA3194438@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 198 bytes --]
libstdc++-v3/ChangeLog:
PR libstdc++/92285
* doc/xml/manual/evolution.xml: Document change to base class.
* doc/html/manual/api.html: Regenerate.
Tested powerpc64le-linux. Committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1228 bytes --]
commit 3ef33e756a65484a17abb95ef0d4133f80c014b1
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Nov 4 12:45:32 2020
libstdc++: Document istreambuf_iterator base class change [PR 92285]
libstdc++-v3/ChangeLog:
PR libstdc++/92285
* doc/xml/manual/evolution.xml: Document change to base class.
* doc/html/manual/api.html: Regenerate.
diff --git a/libstdc++-v3/doc/xml/manual/evolution.xml b/libstdc++-v3/doc/xml/manual/evolution.xml
index 38f11b0300d4..55b8903baff5 100644
--- a/libstdc++-v3/doc/xml/manual/evolution.xml
+++ b/libstdc++-v3/doc/xml/manual/evolution.xml
@@ -972,6 +972,15 @@ now defaults to zero.
be used instead.
</para>
+<para>
+ The type of the <classname>std::iterator</classname> base class of
+ <classname>std::istreambuf_iterator</classname> was changed to be
+ consistent for all <option>-std</option> modes.
+ Before GCC 10.1 the base class had one type in C++98 mode and a
+ different type in C++11 and later modes. The type in C++98 mode
+ was changed to be the same as for C++11 and later.
+</para>
+
<para>
Experimental C++2a support improved, with new headers
<filename class="headerfile"><concepts></filename>,
reply other threads:[~2020-11-04 12:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201104125950.GA3194438@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).