public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Document new libstdc++ header dependency changes
Date: Mon, 16 Jan 2023 10:50:01 +0000	[thread overview]
Message-ID: <20230116105001.13048-1-jwakely@redhat.com> (raw)

Pushed to wwwdocs.

-- >8 --

---
 htdocs/gcc-13/porting_to.html | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index 7a67c0b0..9a9a3147 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -34,12 +34,26 @@ 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 when compiled with GCC 13:
+be included explicitly when compiling with GCC 13:
 </p>
 <ul>
+<li> <code>&lt;string&gt;</code>
+  (for <code>std::string</code>, <code>std::to_string</code>,
+  <code>std::stoi</code> etc.)
+</li>
+<li> <code>&lt;system_error&gt;</code>
+  (for <code>std::error_code</code>, <code>std::error_category</code>,
+  <code>std::system_error</code>).
+</li>
 <li> <code>&lt;cstdint&gt;</code>
   (for <code>std::int8_t</code>, <code>std::int32_t</code> etc.)
 </li>
+<li> <code>&lt;cstdio&gt;</code>
+  (for <code>std::printf</code>, <code>std::fopen</code> etc.)
+</li>
+<li> <code>&lt;cstdlib&gt;</code>
+  (for <code>std::strtol</code>, <code>std::malloc</code> etc.)
+</li>
 </ul>
 
 <h3 id="P2266">Implicit move rules change</h3>
-- 
2.39.0


                 reply	other threads:[~2023-01-16 10:50 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=20230116105001.13048-1-jwakely@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).