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.)
