|Ignore break line sometimes firstname.lastname@example.org (Geovani de Souza) (2012-02-11)|
|Re: Ignore break line sometimes DrDiettrich1@aol.com (Hans-Peter Diettrich) (2012-02-11)|
|Re: Ignore break line sometimes email@example.com (George Neuner) (2012-02-11)|
|Re: Ignore break line sometimes firstname.lastname@example.org (Stefan Monnier) (2012-02-12)|
|Re: Ignore break line sometimes Pidgeot18@verizon.invalid (Joshua Cranmer) (2012-02-12)|
|Re: Ignore break line sometimes email@example.com (Kaz Kylheku) (2012-02-13)|
|Re: Ignore break line sometimes firstname.lastname@example.org (BartC) (2012-02-14)|
|Re: Ignore break line sometimes email@example.com (Gene Wirchenko) (2012-02-19)|
|Re: Ignore break line sometimes firstname.lastname@example.org (glen herrmannsfeldt) (2012-02-20)|
|Re: Ignore break line sometimes email@example.com (2012-02-23)|
|Re: Ignore break line sometimes firstname.lastname@example.org (Jonathan Thornburg) (2012-02-27)|
|From:||Gene Wirchenko <email@example.com>|
|Date:||Sun, 19 Feb 2012 20:57:51 -0800|
|Organization:||A noiseless patient Spider|
|Posted-Date:||20 Feb 2012 01:52:55 EST|
On Sun, 12 Feb 2012 12:03:13 -0600, Joshua Cranmer
>It sounds like you want something like ECMAScript's magic
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
<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 to the
Search the comp.compilers archives again.