Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.42!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!198.186.194.250.MISMATCH!news-out.readnews.com!news-xxxfer.readnews.com!news.misty.com!news.iecc.com!nerds-end
From: Gene Wirchenko <genew@ocis.net>
Newsgroups: comp.compilers
Subject: Re: Ignore break line sometimes
Date: Sun, 19 Feb 2012 20:57:51 -0800
Organization: A noiseless patient Spider
Lines: 28
Sender: johnl@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <12-02-023@comp.compilers>
References: <12-02-010@comp.compilers> <12-02-017@comp.compilers>
NNTP-Posting-Host: news.iecc.com
X-Trace: leila.iecc.com 1329720775 84229 64.57.183.58 (20 Feb 2012 06:52:55 GMT)
X-Complaints-To: abuse@iecc.com
NNTP-Posting-Date: Mon, 20 Feb 2012 06:52:55 +0000 (UTC)
Keywords: parse
Posted-Date: 20 Feb 2012 01:52:55 EST
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
Xref: x330-a1.tempe.blueboxinc.net comp.compilers:463

On Sun, 12 Feb 2012 12:03:13 -0600, Joshua Cranmer
<Pidgeot18@verizon.invalid> wrote:

[snip]

>It sounds like you want something like ECMAScript's magic
>you-don't-always-need-a-semicolon feature.

     But please do not go there.

><http://bclary.com/2004/11/07/#a-7.9> describes how it works in detail.
>The thrust of it is that "if you see an invalid token, but you saw a
>newline before, automatically insert a semicolon to fix things."
>
>There are more than a few people who believe that this feature should
>not have been implemented.

     There is a bit more to this.  As a result of this kludge, it is
illegal to have newlines at certain points in some statements.  For
example:
          return
           <expression which I decided to put all on its own line>;
is not legal.  It is not permitted to have a newline immediately after
"return".

Sincerely,

Gene Wirchenko