Path: csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: "Robin Vowels" Newsgroups: comp.compilers Subject: Re: Keywords and Reserved Words Date: Thu, 10 Mar 2022 09:55:46 +1100 Organization: Compilers Central Lines: 10 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <22-03-021@comp.compilers> References: <22-03-004@comp.compilers> <22-03-009@comp.compilers> <22-03-015@comp.compilers> <22-03-016@comp.compilers> <22-03-017@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 8bit Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="64703"; mail-complaints-to="abuse@iecc.com" Keywords: Fortran, parse, comment Posted-Date: 09 Mar 2022 20:53:53 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:2925 > [If anyone wants to know how to find the tokens in old space-insensitive Fortran > I can tell you, but it's as ugly as you might imagine. -John] No it's not. See A. H. J. Sale, "The Classification of FORTRAN Statements", Computer Journal, Vol. 14 No. 1, 1971. [Having written production Fortran compilers, I can assure you that to do it right is quite ugly. I looked at the article and he missed some things, and he made some unrealistic assumptions that a compiler would accept nothing beyond what was in the Basic Fortran standard. -John]