bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: Bjarni Ingi Gislason <bjarniig@simnet.is>
Subject: Re: module c-nullptr: error compiling groff
Date: Sun, 5 Feb 2023 21:10:58 -0800	[thread overview]
Message-ID: <6b80b21b-1449-1de6-d8bb-b27a104c68c6@cs.ucla.edu> (raw)
In-Reply-To: <6051252.riuWyFgYyT@nimes>

Thanks for fixing it so quickly.

On 2023-02-05 19:27, Bruno Haible wrote:

> +# ifdef __cplusplus
> +/* For the C++ compiler the result of the configure test is irrelevant.
> +   We know that at least g++ and clang with option -std=c++11 or higher, as well
> +   as MSVC 14 or newer, already have nullptr.  */
> +#  if !(((defined __GNUC__ || defined __clang__) && __cplusplus >= 201103L) \
> +        || (defined _MSC_VER && 1900 <= _MSC_VER))

<https://en.cppreference.com/w/cpp/language/nullptr> says nullptr is 
part of C++11, so would it be better to omit the "(defined __GNUC__ || 
defined __clang__) && "? It seems unlikely that a compiler would 
advertise conformance to C++11 without supporting nullptr.

  reply	other threads:[~2023-02-06  5:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  0:22 module c-nullptr: error compiling groff Bjarni Ingi Gislason
2023-02-06  3:27 ` Bruno Haible
2023-02-06  5:10   ` Paul Eggert [this message]
2023-02-06 11:13     ` Bruno Haible
2023-02-07 21:50     ` 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:

  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=6b80b21b-1449-1de6-d8bb-b27a104c68c6@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bjarniig@simnet.is \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \


* 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).