public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Jonathan Wakely via Libstdc++ <libstdc++@gcc.gnu.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Document libstdc++ header dependency changes
Date: Thu, 26 Nov 2020 11:53:37 +0000	[thread overview]
Message-ID: <20201126115337.GK1312820@redhat.com> (raw)
In-Reply-To: <20201126113309.GA2103723@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 174 bytes --]

On 26/11/20 11:33 +0000, Jonathan Wakely via Libstdc++ wrote:
>Also explain how to replace dynamic exception specifications.

And a small correction.

Committed to wwwdocs.


[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1429 bytes --]

commit df8e807fa3d534472e1b2084b5fcfc761888ccbc
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Nov 26 11:51:57 2020 +0000

    Fix typo and wording of previous commit

diff --git a/htdocs/gcc-11/porting_to.html b/htdocs/gcc-11/porting_to.html
index 91cd0b4d..41efc3b6 100644
--- a/htdocs/gcc-11/porting_to.html
+++ b/htdocs/gcc-11/porting_to.html
@@ -95,19 +95,18 @@ GCC 11 now enforces that comparison objects be invocable as const.
 <p>Some C++ Standard Library headers have been changed to no longer include
 other headers that they do need to depend on.
 As such, C++ programs that used standard library components without
-including the right headers will no longer compiler.
+including the right headers will no longer compile.
 </p>
 <p>
 The following headers are used less widely in libstdc++ and may need to
-be included explicitly by programs that were incorrectly relying on them
-being included implicitly by other headers:
+be included explicitly when compiled with GCC 11:
 </p>
 <ul>
 <li> <code>&lt;limits&gt;</code>
-  (e.g. for <code>std::numeric_limits</code>)
+  (for <code>std::numeric_limits</code>)
 </li>
 <li> <code>&lt;memory&gt;</code>
-  (e.g. for <code>std::unique_ptr</code>, <code>std::shared_ptr</code> etc.)
+  (for <code>std::unique_ptr</code>, <code>std::shared_ptr</code> etc.)
 </li>
 <li> <code>&lt;utility&gt;</code>
   (for <code>std::pair</code>, <code>std::tuple_size</code>,

  reply	other threads:[~2020-11-26 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 11:33 Jonathan Wakely
2020-11-26 11:53 ` Jonathan Wakely [this message]
2020-12-01 21:58   ` Gerald Pfeifer
2020-12-01 22:06     ` Jeff Law

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=20201126115337.GK1312820@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).