This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: resolving backslash newline whisky tango foxtrot: a proposal


Joe Buck wrote:
On Sat, Oct 29, 2005 at 03:45:33AM -0700, Per Bothner wrote:

1. Change the behavior (back) so only '\\$', not '\\ *$', causes a
  line to be continued.

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

My hope was that an improved on-by-default -Wcomment would catch that. I.e. it would warn about any code that act be differently depending on whether trailing whitspace is removed.

Any code and only code that starts getting the warning is at risk.
--
	--Per Bothner
per@bothner.com   http://per.bothner.com/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]