bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Cc: Bjarni Ingi Gislason <bjarniig@simnet.is>
Subject: Re: module c-nullptr: error compiling groff
Date: Tue, 07 Feb 2023 22:50:52 +0100	[thread overview]
Message-ID: <2077662.L1XL2SkS6N@nimes> (raw)
In-Reply-To: <6b80b21b-1449-1de6-d8bb-b27a104c68c6@cs.ucla.edu>

Paul Eggert wrote:
> It seems unlikely that a compiler would 
> advertise conformance to C++11 without supporting nullptr.

Here's a case where a compiler advertises conformance to C++11 without
supporting all that's needed:
https://bugs.llvm.org/show_bug.cgi?id=44871

I'm sure there are more examples like this.

Bruno





      parent reply	other threads:[~2023-02-07 21:51 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
2023-02-06 11:13     ` Bruno Haible
2023-02-07 21:50     ` Bruno Haible [this message]

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=2077662.L1XL2SkS6N@nimes \
    --to=bruno@clisp.org \
    --cc=bjarniig@simnet.is \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).