Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED!nerds-end From: George Neuner Newsgroups: comp.compilers Subject: Re: Programming language and IDE design Date: Tue, 19 Nov 2013 12:41:54 -0500 Organization: A noiseless patient Spider Lines: 16 Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <13-11-021@comp.compilers> References: <13-11-016@comp.compilers> <13-11-018@comp.compilers> NNTP-Posting-Host: news.iecc.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: leila.iecc.com 1384885420 55594 64.57.183.58 (19 Nov 2013 18:23:40 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Tue, 19 Nov 2013 18:23:40 +0000 (UTC) Keywords: Fortran, parse, comment Posted-Date: 19 Nov 2013 13:23:40 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1045 Our esteemed moderator wrote: >[Fortran through F77 potentially had to look arbitrarily far ahead to >tell FORMAT statements from an assignment to an array called FORMAT. >BTDT. But I would be surprised if any modern languages were that hard >to lex. -John] You're right - I forgot that the FORMAT *statement* also could be confused with an assignment [I only ever used format strings with READ and WRITE]. That potentially could require a large lookahead. But it's still LL(k). 8-) George [Oh, sure, once you know whether a statement is an assignment or something else, parsing is trivial. -John]