From: Bruno Haible <bruno@clisp.org>
To: noloader@gmail.com, Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: assert-h: Make static_assert work on Solaris 11.4
Date: Tue, 25 Oct 2022 22:11:09 +0200 [thread overview]
Message-ID: <6616587.hy9JHpt1j4@nimes> (raw)
In-Reply-To: <780a1582-5d93-d7e5-c12c-7bef8654a0d6@cs.ucla.edu>
Paul Eggert wrote:
> > Re: the ellipses. From
> > https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2264r3.html,
> > Section 8:
>
> Thanks. Although that sort of explains things, it doesn't explain why
> the latest draft uses ellipses only when NDEBUG is defined. Shouldn't
> ellipses also be used when NDEBUG is not defined?
That's exactly what the standard says in § 7.2.(2):
The assert macro shall be implemented as a macro with an ellipsis parameter,
not as an actual function.
Bruno
next prev parent reply other threads:[~2022-10-25 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 14:47 assert-h: Make static_assert work on Solaris 11.4 Bruno Haible
2022-10-25 18:12 ` Paul Eggert
2022-10-25 18:18 ` Jeffrey Walton
2022-10-25 18:22 ` Paul Eggert
2022-10-25 20:11 ` Bruno Haible [this message]
2022-10-25 21:47 ` Paul Eggert
2022-10-26 0:17 ` Bruno Haible
2022-10-25 20:05 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6616587.hy9JHpt1j4@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=noloader@gmail.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).