From: Florian Weimer <fweimer@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Peter Johansson <trojkan@gmail.com>,
Zack Weinberg <zack@owlfolio.org>, Autoconf <autoconf@gnu.org>,
gcc@gcc.gnu.org
Subject: Re: configure adds -std=gnu++11 to CXX variable
Date: Mon, 27 May 2024 12:35:20 +0200 [thread overview]
Message-ID: <878qzv1r13.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <80bf1a5a-63a3-4da4-8721-88c760243add@cs.ucla.edu> (Paul Eggert's message of "Sun, 26 May 2024 09:31:53 -0700")
* Paul Eggert:
> diff --git a/NEWS b/NEWS
> index 20dbc173..4ba8f3fe 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -16,6 +16,10 @@ GNU Autoconf NEWS - User visible changes.
> C11 and later. Programs can use AC_C_VARARRAYS and __STDC_NO_VLA__
> to use VLAs if available.
>
> +*** AC_PROG_CXX now prefers C++23, C++20, C++17, C++14 if available.
> + Older code may need to be updated, as some older features of C++ are
> + removed in later standards.
> +
Does this turn on experimental language modes by default? That's
probably not what we want.
It would be better to have an option to raise the C++ mode to at least a
certain revision, and otherwise use the default. The default is more
likely to be supported by system libraries, and it's a bit less likely
that programmers use experimental, known-to-be-buggy features (language
and library) by accident.
Thanks,
Florian
next parent reply other threads:[~2024-05-27 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEZXgxjf7fQNHvkA09ia8ivHEsOHVKhzvoqdq=TCNRfdFTJryA@mail.gmail.com>
[not found] ` <aece3efd-503b-4106-99ad-e66be8b0b684@app.fastmail.com>
[not found] ` <00dc6e30-2e12-4b29-951b-d600097b38d0@gmail.com>
[not found] ` <80bf1a5a-63a3-4da4-8721-88c760243add@cs.ucla.edu>
2024-05-27 10:35 ` Florian Weimer [this message]
2024-05-27 19:04 ` Paul Eggert
2024-05-27 19:18 ` Jakub Jelinek
2024-05-28 1:50 ` Paul Eggert
2024-05-28 8:20 ` Jonathan Wakely
2024-05-28 14:35 ` Paul Eggert
2024-05-28 15:01 ` Jason Merrill
2024-05-28 15:02 ` Jakub Jelinek
2024-05-28 16:44 ` Joseph Myers
2024-05-28 16:45 ` Paul Eggert
2024-05-28 18:27 ` Jason Merrill
2024-05-28 20:09 ` Paul Eggert
2024-05-29 17:33 ` Tom Tromey
2024-05-29 17:40 ` Jason Merrill
2024-05-28 6:23 ` Florian Weimer
2024-05-28 8:15 ` Jonathan Wakely
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=878qzv1r13.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=autoconf@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=gcc@gcc.gnu.org \
--cc=trojkan@gmail.com \
--cc=zack@owlfolio.org \
/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).