From: Marc Glisse <marc.glisse@inria.fr>
To: SHIH YEN-TE <shihyente@hotmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: About Bug 52485
Date: Wed, 09 May 2018 08:41:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1805091039100.17103@stedding.saclay.inria.fr> (raw)
In-Reply-To: <BL0PR20MB2067F524AE80917B4C8DA3ECB6990@BL0PR20MB2067.namprd20.prod.outlook.com>
On Wed, 9 May 2018, SHIH YEN-TE wrote:
> Want to comment on "Bug 52485 - [c++11] add an option to disable c++11
> user-defined literals"
>
> It's a pity GCC doesn't support this, which forces me to give up
> introducing newer C++ standard into my project. I know it is ridiculous,
> but we must know the real world is somehow ridiculous as well as nothing
> is perfect.
You have the wrong approach.
Apparently, you are using an unmaintained library (if it was maintained,
it would be compatible with C++11 by now), so there is no problem
modifying it, especially just to add a few spaces. A single run of
clang-tidy would likely fix all of them for you.
--
Marc Glisse
next prev parent reply other threads:[~2018-05-09 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 8:12 SHIH YEN-TE
2018-05-09 8:41 ` Marc Glisse [this message]
2018-05-09 8:42 ` Will Hawkins
2018-05-09 8:58 ` 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=alpine.DEB.2.21.1805091039100.17103@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc@gcc.gnu.org \
--cc=shihyente@hotmail.com \
/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).