public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: redi@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. b1bd21c81af3bc3098fca4293af164a6c6a4544a
Date: Fri, 24 Jan 2020 15:30:00 -0000	[thread overview]
Message-ID: <20200124153053.113938.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  b1bd21c81af3bc3098fca4293af164a6c6a4544a (commit)
       via  8fdda0b261bcd59e3bed41228fe9ced40ad1397f (commit)
      from  f526c4724b183482fc7fe1a5ce78e1597fd1005f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit b1bd21c81af3bc3098fca4293af164a6c6a4544a
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Jan 24 15:30:06 2020 +0000

    Make it clear C++2a support is experimental

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index ef27c9bb..dcce6b86 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -331,7 +331,7 @@ a work-in-progress.</p>
 
 <h4 id="libstdcxx">Runtime Library (libstdc++)</h4>
 <ul>
-  <li>Improved C++2a support, including:
+  <li>Improved experimental C++2a support, including:
     <ul>
       <li> <code>std::span</code> (thanks to JeanHeyd Meneide). </li>
       <li>

commit 8fdda0b261bcd59e3bed41228fe9ced40ad1397f
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Jan 24 15:29:46 2020 +0000

    Document C++ header reorganisation

diff --git a/htdocs/gcc-10/porting_to.html b/htdocs/gcc-10/porting_to.html
index 7d45a962..980d3af1 100644
--- a/htdocs/gcc-10/porting_to.html
+++ b/htdocs/gcc-10/porting_to.html
@@ -49,6 +49,26 @@ and provide solutions. Let us know if you have suggestions for improvements!
       extern int y;  // correct declaration in a header file
   </code></pre>
 
+
+<h2 id="cxx">C++ language issues</h2>
+
+<h3 id="header-dep-changes">Header dependency changes</h3>
+
+<p>Some C++ Standard Library headers have been changed to no longer include
+the <code>&lt;stdexcept&gt;</code> header.
+As such, C++ programs that used components defined in
+<code>&lt;stdexcept&gt;</code> or <code>&lt;string&gt;</code> without
+explicitly including the right headers will no longer compile.
+</p>
+<p>
+Previously components such as <code>std::runtime_error</code>,
+<code>std::string</code> and <code>std::allocator</code>
+were implicitly defined after including unrelated headers such as
+<code>&lt;array&gt;</code> and <code>&lt;optional&gt;</code>.
+Correct code should include the appropriate headers for the classes being used.
+</p>
+
+
 <h2 id="fortran">Fortran language issues</h2>
 
 <h3 id="argument-mismatch">Argument mismatches</h3>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/changes.html    |  2 +-
 htdocs/gcc-10/porting_to.html | 20 ++++++++++++++++++++
 2 files changed, 21 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-24 15:30 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=20200124153053.113938.qmail@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs-wwwdocs@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).