For what it's worth, my opinion: A program whose semantics depends on invisible end-of-line whitespace is erroneous and a disaster waiting to happen.
The portability argument wrt other compilers is all very well, but the code fails to be portable in so many other ways, as people have mentioned: cut-and-paste; web archives; reading printed-out code; not to mention virtual 80-column punch cards on VM/CMS ... I'd like to keep the current behavior, but add a warning, which should default to on. I'll go along with a compromise: change the behavior to match the "other compilers", as along as a warning is emitted. The warning can be turned off with our generic turn-off-specific-warnings framework (I'm so out of gcc development I'm not sure we have one - but I vaguely remember reading about it). However, the warning should be on by default. -- --Per Bothner [EMAIL PROTECTED] http://per.bothner.com/