From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Roland Illig <roland.illig@gmx.de>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: terminology: zero character vs. null character
Date: Fri, 10 Mar 2017 08:06:00 -0000 [thread overview]
Message-ID: <43e59cbc-4352-af0a-90f1-112b1ae5301a@gmail.com> (raw)
In-Reply-To: <24d86a2d-02c2-7774-7876-73b7825c7811@gmx.de>
On 06/03/17 21:15, Roland Illig wrote:
> Hi,
>
> I am currently translating GCC into German. During that, I noticed that
> in some places the term "zero character" means '\0'. The official term
> though is "null character", as per the C standard.
>
> Since it is confusing to have two different terms for the same concept,
> the term "zero character" should be dropped entirely, both because it is
> uncommon and because it can be confused with '0'.
>
> Since this affects several places in the code, I think it's better to
> start a small discussion first instead of writing several PRs.
I don't see anything explicit here: https://gcc.gnu.org/codingconventions.html
But I believe we follow standards' language and it should always be "null
character". Having a discussion first is likely to get nowhere. It sounds too
much like "maybe we should" (point 11: https://gcc.gnu.org/wiki/Community).
Please send a patch fixing it:
https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps
You can also send a patch changing https://gcc.gnu.org/codingconventions.html.
Once that is accepted, obvious changes to match the coding conventions are
usually considered pre-approved.
Cheers,
Manuel.
next prev parent reply other threads:[~2017-03-10 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 21:16 Roland Illig
2017-03-10 8:06 ` Manuel López-Ibáñez [this message]
2017-03-12 21:28 ` Gerald Pfeifer
2017-03-13 18:15 ` Joseph Myers
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=43e59cbc-4352-af0a-90f1-112b1ae5301a@gmail.com \
--to=lopezibanez@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=roland.illig@gmx.de \
/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).