[Bug preprocessor/8270] [4.7/4.8/4.9 Regression] back-slash white space newline with comments, no warning

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

[Bug preprocessor/8270] [4.7/4.8/4.9 Regression] back-slash white space newline with comments, no warning

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 f

[Bug preprocessor/8270] [4.7/4.8/4.9 Regression] back-slash white space newline with comments, no warning

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 delete

[Bug preprocessor/8270] [4.7/4.8/4.9 Regression] back-slash white space newline with comments, no warning

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