Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin1!goblin.stu.neva.ru!postnews.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!nerds-end From: glen herrmannsfeldt Newsgroups: comp.compilers Subject: Re: Ignore break line sometimes Date: Mon, 20 Feb 2012 08:09:07 +0000 (UTC) Organization: Aioe.org NNTP Server Lines: 29 Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-02-024@comp.compilers> References: <12-02-010@comp.compilers> <12-02-017@comp.compilers> <12-02-023@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: leila.iecc.com 1329898626 92269 64.57.183.58 (22 Feb 2012 08:17:06 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Wed, 22 Feb 2012 08:17:06 +0000 (UTC) Keywords: parse Posted-Date: 22 Feb 2012 03:17:06 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:464 Gene Wirchenko wrote: (snip, someone wrote) >> 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 > ; > is not legal. It is not permitted to have a newline immediately after > "return". Sounds about like the way IBM's JCL from OS/360 and successors works. You can split a statement after a comma in most cases, and continue it on the next line, after the usual // and some spaces. I believe the original (early) versions had a more usual system with a continuation character in column 72, and then start the next statement in column 16. I presume it was found hard to get right so they changed it. I believe that there are a few other languages with a similar continuation method. That is, if you end a statement in a legal end, no continuation is needed. -- glen