From: Paul Eggert <eggert@cs.ucla.edu>
To: noloader@gmail.com
Cc: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: assert-h: Make static_assert work on Solaris 11.4
Date: Tue, 25 Oct 2022 11:22:48 -0700 [thread overview]
Message-ID: <780a1582-5d93-d7e5-c12c-7bef8654a0d6@cs.ucla.edu> (raw)
In-Reply-To: <CAH8yC8=WGJhBK+QCywRp_F4J2dZkrNMqdhFg7gvx5c5B5bipNQ@mail.gmail.com>
On 2022-10-25 11:18, Jeffrey Walton 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?
Sounds like another typo (or at least lack of clarity) in the current draft.
next prev parent reply other threads:[~2022-10-25 18:23 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 [this message]
2022-10-25 20:11 ` Bruno Haible
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=780a1582-5d93-d7e5-c12c-7bef8654a0d6@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--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).