public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 7648e9e0869aaf51ac53c8430bc603474d8a88f3 Date: Wed, 11 Aug 2021 00:35:16 +0000 (GMT) [thread overview] Message-ID: <20210811003516.AEEE1385DC10@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 7648e9e0869aaf51ac53c8430bc603474d8a88f3 (commit) from b0b06710297dd9b104d095a7ccab51e2e30f27b0 (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 7648e9e0869aaf51ac53c8430bc603474d8a88f3 Author: Jason Merrill <jason@redhat.com> Date: Tue Aug 10 20:34:40 2021 -0400 Update "export" entry in nonbugs diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index 80dac392..0a1b582a 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -536,12 +536,13 @@ for details. <dl> <dt><code>export</code></dt> -<dd><p>Most C++ compilers (G++ included) do not yet implement -<code>export</code>, which is necessary for separate compilation of -template declarations and definitions. Without <code>export</code>, a -template definition must be in scope to be used. The obvious -workaround is simply to place all definitions in the header -itself. Alternatively, the compilation unit containing template +<dd><p>Most C++ compilers (G++ included) never implemented C++98 +<code>export</code>, which was removed in C++11, and the keyword reused in +C++20 by the Modules feature. The C++98 feature was intended to support +separate compilation of template declarations and +definitions. Without <code>export</code>, a template definition must be in +scope to be used. The obvious workaround is simply to place all definitions in +the header itself. Alternatively, the compilation unit containing template definitions may be included from the header.</p></dd> <dt>Nested classes can access private members and types of the containing ----------------------------------------------------------------------- Summary of changes: htdocs/bugs/index.html | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-08-11 0:35 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=20210811003516.AEEE1385DC10@sourceware.org \ --to=jason@sourceware.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: linkBe 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).