http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
--- Comment #51 from GoWhoopee at yahoo dot com ---
http://web.cs.dal.ca/~vlado/pl/C_Standard_2011-n1570.pdf
That's the principle, but not what happens with gcc...
Phase 2 says, Each instance of a backslash character (\) immediately followed
by a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
--- Comment #52 from GoWhoopee at yahoo dot com ---
Whitespace is required by Translation Phase 3, consequently Translation Phase 1
should not be changing whitespace at all, only mapping multibyte characters and
trigraphs.
Comment #39: Indicates
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
--- Comment #49 from GoWhoopee at yahoo dot com ---
I've read all the comments and all those on linked forums and I have no idea
how you struggle with this!
If a compiler changes backslash space into backslash newline and consequently
deletes the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
Mikael Pettersson mikpelinux at gmail dot com changed:
What|Removed |Added
CC||mikpelinux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
GoWhoopee at yahoo dot com changed:
What|Removed |Added
CC||GoWhoopee at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
--- Comment #48 from Andrew Pinski pinskia at gcc dot gnu.org ---
(In reply to GoWhoopee from comment #47)
Please reconsider and stop gcc from changing our code without our permission.
It is not changing your code at all. Read comment #39 to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8270
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|4.6.4 |4.7.4
