public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Lewis Hyatt <lhyatt@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 4ad719cc7b3aa8eee9692bc2f291f543ab39b63a Date: Fri, 1 May 2020 14:31:19 +0000 (GMT) [thread overview] Message-ID: <20200501143119.70E473898528@sourceware.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1589 bytes --] 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 4ad719cc7b3aa8eee9692bc2f291f543ab39b63a (commit) from 3f573b5fe7df858a27b0275edc5fd4386804ae83 (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 4ad719cc7b3aa8eee9692bc2f291f543ab39b63a Author: Lewis Hyatt <lhyatt@gmail.com> Date: Tue Jan 14 18:52:20 2020 -0500 Document support for extended identifiers added to GCC 10 in changes.html diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index a3cf19cc..4497be14 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -252,6 +252,15 @@ a work-in-progress.</p> </li> </ul> </li> + <li>Extended characters in identifiers may now be specified directly in + the input encoding (UTF-8, by default), in addition to the UCN syntax + (<code>\uNNNN</code> or <code>\UNNNNNNNN</code>) that is already + supported: + <blockquote><pre> +static const int π = 3; +int get_naïve_pi() { + return π; +}</pre></blockquote></li> </ul> <h3 id="c">C</h3> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 9 +++++++++ 1 file changed, 9 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-05-01 14:31 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=20200501143119.70E473898528@sourceware.org \ --to=lhyatt@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).