From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Dmitri Gribenko <gribozavr@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
gcc@gcc.gnu.org, cfe-dev <cfe-dev@lists.llvm.org>
Subject: Re: [cfe-dev] ISO C3X proposal: nonnull qualifier
Date: Thu, 2 Dec 2021 02:00:28 +0100 [thread overview]
Message-ID: <f1d3b8a6-0a2c-596c-6213-9d3cf28efc46@gmail.com> (raw)
In-Reply-To: <CA+Y5xYey6PVEJoxNzWubgkbpzPmMtyk3YadwW9X2Xswnq0oXNA@mail.gmail.com>
Hi Dmitri
On 12/2/21 01:39, Dmitri Gribenko wrote:
>>> Pre-C3X headers won't work correctly when included in C3X programs,
>>> making incremental adoption of C3X syntax, as it was intended to be
>>> used, impossible. Projects would likely invent a NULLABLE macro, which
>>> would expand to _Nullable in C3X and nothing in earlier versions, to
>>> enable an incremental transition.
>>>
>>> That's why Clang introduced the pragma, enabling new rules to be
>>> adopted incrementally.
>>
>> Let's avoid forking C :)
>
> Do you consider the standard pragma `#pragma STDC FENV_ACCESS` to be a
> language fork? If not, why is a pragma to control nullability of
> pointers different?
Sorry, I put the reply at a wrong point in the quote. I didn't refer to
the pragma, but the the previous paragraph. Basically, I meant let's
not add _Nullable to C3X, and add just _Nonnull.
Cheers,
Alex
next prev parent reply other threads:[~2021-12-02 1:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:01 Alejandro Colomar (man-pages)
2021-11-15 16:30 ` Alejandro Colomar (man-pages)
2021-11-15 20:18 ` Joseph Myers
2021-11-15 21:09 ` Alejandro Colomar (man-pages)
2021-11-15 22:17 ` Joseph Myers
2021-11-15 22:35 ` Alejandro Colomar (man-pages)
2021-11-15 22:47 ` Joseph Myers
2021-11-16 12:34 ` Alejandro Colomar (man-pages)
2021-11-17 0:06 ` Alejandro Colomar (man-pages)
2021-11-20 16:47 ` Ping: " Alejandro Colomar (man-pages)
2021-11-23 11:32 ` [cfe-dev] " Dmitri Gribenko
2021-11-23 11:17 ` Dmitri Gribenko
2021-11-23 11:45 ` Alejandro Colomar (man-pages)
2021-11-23 12:45 ` Dmitri Gribenko
2021-12-01 22:24 ` Alejandro Colomar (man-pages)
2021-12-02 0:39 ` Dmitri Gribenko
2021-12-02 1:00 ` Alejandro Colomar (man-pages) [this message]
2021-12-02 20:24 ` Alejandro Colomar (man-pages)
2021-12-02 20:31 ` Alejandro Colomar (man-pages)
2021-12-02 20:36 ` Joseph Myers
2021-11-16 9:30 ` Jonathan Wakely
2021-11-16 17:13 ` [cfe-dev] " Arthur O'Dwyer
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=f1d3b8a6-0a2c-596c-6213-9d3cf28efc46@gmail.com \
--to=alx.manpages@gmail.com \
--cc=cfe-dev@lists.llvm.org \
--cc=gcc@gcc.gnu.org \
--cc=gribozavr@gmail.com \
--cc=joseph@codesourcery.com \
/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).