From: Maciej Cencora <m.cencora@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Fix uses of non-reserved names in headers
Date: Thu, 16 Feb 2023 14:23:48 +0100 [thread overview]
Message-ID: <CAPFqmUrzWxQGEV8_knNQYPeOuoCfwb90ipOW1CgF7hVWdo1m2w@mail.gmail.com> (raw)
Hi,
instead of uglyfing all the libstdc++ code wouldn't it be simpler to
just ignore all non-reserved macro expansions (+ some special ones
like assert) inside system headers on compiler level?
Regards,
Maciej
next reply other threads:[~2023-02-16 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 13:23 Maciej Cencora [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-16 10:30 Jonathan Wakely
2023-02-16 10:47 ` Jakub Jelinek
2023-02-16 11:45 ` Jakub Jelinek
2023-02-16 12:02 ` Jonathan Wakely
2023-02-16 12:00 ` 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=CAPFqmUrzWxQGEV8_knNQYPeOuoCfwb90ipOW1CgF7hVWdo1m2w@mail.gmail.com \
--to=m.cencora@gmail.com \
--cc=gcc-patches@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).