public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "GoWhoopee at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/8270] [4.7/4.8/4.9 Regression] back-slash white space newline with comments, no warning
Date: Thu, 12 Dec 2013 08:24:00 -0000	[thread overview]
Message-ID: <bug-8270-4-kesGBTCKO2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-8270-4@http.gcc.gnu.org/bugzilla/>

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 newline it is changing the meaning of the code!

All other development environments people here have used don't do this and gcc
shouldn't!

Here's an example of code your compiler changes:

#define HIGH_SPEED_TURRET   // \ 
#define SAFETY_LOCKED_ON    //  >------------- Critical Configuration
#define NEVER_PRIME_MISSILE // /

The programmer put backslash space and the syntax highlighter correctly showed
the safety was locked on.

Sleep well.


  parent reply	other threads:[~2013-12-12  8:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8270-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 12:16 ` [Bug preprocessor/8270] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-13 12:47 ` [Bug preprocessor/8270] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 12:40 ` [Bug preprocessor/8270] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2013-04-12 15:15 ` [Bug preprocessor/8270] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-12-11 12:41 ` GoWhoopee at yahoo dot com
2013-12-11 18:33 ` pinskia at gcc dot gnu.org
2013-12-12  8:24 ` GoWhoopee at yahoo dot com [this message]
2013-12-12 15:02 ` mikpelinux at gmail dot com
2013-12-13  8:15 ` GoWhoopee at yahoo dot com
2013-12-13 10:48 ` GoWhoopee at yahoo dot com
2014-06-12 13:41 ` [Bug preprocessor/8270] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:23 ` [Bug preprocessor/8270] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-03-19 14:21 ` ktietz at gcc dot gnu.org
2015-03-21 15:25 ` doug at cs dot dartmouth.edu
2015-03-23  9:49 ` ktietz at gcc dot gnu.org
2015-06-23  8:12 ` [Bug preprocessor/8270] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 19:51 ` [Bug preprocessor/8270] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:25 ` jakub at gcc dot gnu.org
2021-05-14  9:45 ` [Bug preprocessor/8270] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:03 ` rguenth at gcc dot gnu.org
2022-05-27  9:33 ` [Bug preprocessor/8270] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:28 ` jakub at gcc dot gnu.org
2023-07-07 10:28 ` [Bug preprocessor/8270] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-10 12:09 ` verodeving at gmail 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-8270-4-kesGBTCKO2@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).