This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: resolving backslash newline whisky tango foxtrot: a proposal
On Sat, Oct 29, 2005 at 03:45:33AM -0700, Per Bothner wrote:
> Rather than adding new flags, I'd think I'd prefer:
>
> 1. Change the behavior (back) so only '\\$', not '\\ *$', causes a
> line to be continued.
> 2. Make -Wcomment more useful to it only warns when it might matter:
> The following line contains non-comment whitespace.
> 3. Make -Wcomment the default - not just for -Wall, but always.
> It can be turned off with -Wno-comment
Your item #2 was part of my (amended) proposal (the first version had
a new warning, it was revised to just fix -Wcomment).
#3 would be fine with me.
The problem with your item #1 is that there is then no way of flagging
code that won't work with the large numbers of production compilers
based on gcc 3.x, as well as code that will break if anyone ever removes
trailing whitespace (something that can easily happen in the process
of editing the code). At minimum, it seems that there has to be a
mode, to be compatible with previous gcc releases. Then you're back
to the -f flag, and the only argument is about which should be the
default (and I'm agnostic on that one).