From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Fix several preprocessor directives
Date: Mon, 7 Aug 2023 11:46:12 +0100 [thread overview]
Message-ID: <CACb0b4=K_WbvQ+36Hn8mGPLTWM_i4-BxuxioP_mA+9gKHpcwuA@mail.gmail.com> (raw)
In-Reply-To: <2c5a8abd-c03e-294f-74bc-9e3f3f1de393@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
On Sun, 30 Jul 2023 at 14:55, François Dumont via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:
> Committed as obvious.
>
> libstdc++: Fix several preprocessor directives
>
> A wrong usage of #define in place of a #error seems to have been
> replicated
> at different places in source files.
>
Oops, thanks!
>
> libstdc++-v3/ChangeLog:
>
> * src/c++11/compatibility-ldbl-facets-aliases.h: Replace
> #define with
> proper #error.
> * src/c++11/locale-inst-monetary.h: Likewise.
> * src/c++11/locale-inst-numeric.h: Likewise.
>
> François
>
prev parent reply other threads:[~2023-08-07 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 13:55 François Dumont
2023-08-07 10:46 ` Jonathan Wakely [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACb0b4=K_WbvQ+36Hn8mGPLTWM_i4-BxuxioP_mA+9gKHpcwuA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).