public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52538] Extend C++11 UDLs to be compatible with inttypes.h macros
Date: Fri, 09 Mar 2012 09:52:00 -0000	[thread overview]
Message-ID: <bug-52538-4-OnHox80cy8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52538-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52538

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-03-09 09:51:34 UTC ---
(In reply to comment #1)
> If you want to use C++11, then you have to write C++11 code.  That is the way
> forward I think we have discussed this before.

Yes, in PR 52485, and see also PR 51282 and PR 50917 - this is affecting a lot
of large codebases. The committee are discussing whether this is a defect worth
addressing in the standard, as the scope of the problems is larger than
previously realised.

(In reply to comment #0)
> It would also be possible to fix the code by inserting a space between the "
> and the macro name, but in Google's codebase, this cleanup would be 3-4x as
> large as the narrowing conversion cleanup, which you have already made
> optional.

Ack. When UDL support was added to G++ I also found more problems due to
"PRId64" than I had found when narrowing errors where added (in a much smaller
codebase, obviously.)


  parent reply	other threads:[~2012-03-09  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  9:00 [Bug c++/52538] New: " jyasskin at gcc dot gnu.org
2012-03-09  9:07 ` [Bug c++/52538] " pinskia at gcc dot gnu.org
2012-03-09  9:52 ` redi at gcc dot gnu.org [this message]
2012-04-27 14:29 ` aaw at gcc dot gnu.org
2012-04-27 17:48 ` jyasskin at gcc dot gnu.org
2012-05-01 10:38 ` redi at gcc dot gnu.org
2012-11-12 14:57 ` paolo.carlini at oracle dot com

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=bug-52538-4-OnHox80cy8@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).