Re: PL/I syntax, was Java Comment-Preserving Grammar

Alex Colvin <alexc@std.com>
21 Jun 2004 23:52:08 -0400

          From comp.compilers

Related articles
Java Comment-Preserving Grammar matthew-google@faredge.com.au (2004-05-24)
Re: Java Comment-Preserving Grammar jens.troeger@light-speed.de (2004-06-06)
Re: Java Comment-Preserving Grammar gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-06-09)
Re: Java Comment-Preserving Grammar cfc@shell01.TheWorld.com (Chris F Clark) (2004-06-11)
Re: Java Comment-Preserving Grammar gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-06-13)
Re: Java Comment-Preserving Grammar cfc@shell01.TheWorld.com (Chris F Clark) (2004-06-15)
Re: PL/I syntax, was Java Comment-Preserving Grammar alexc@std.com (Alex Colvin) (2004-06-21)
Re: PL/I syntax, was Java Comment-Preserving Grammar Peter_Flass@Yahoo.com (Peter Flass) (2004-06-26)
| List of all articles for this month |

From: Alex Colvin <alexc@std.com>
Newsgroups: comp.compilers
Date: 21 Jun 2004 23:52:08 -0400
Organization: The World : www.TheWorld.com : Since 1989
References: 04-05-075 04-06-004 04-06-022 04-06-041 04-06-057 04-06-071
Keywords: PL/I, parse, comment
Posted-Date: 21 Jun 2004 23:52:08 EDT

>> ....PL/I has extra excitement beyond tokenizing because it has no
>> reserved words and you can write IF IF=THEN THEN IF=ELSE; ELSE
>> IF=THEN; -John]


aren't isubs such as X(1SUB,2SUB) also special?
Can whitespace appear between the number and "SUB".
I suppose this could be handled as a special ISUB token /[0-9]+SUB/.
Still pretty unusual.


--
mac the naf
[The PL/I standard has a special case for iSUB, and it appears that
you can't put spaces there. You can't put spaces in bit string
constants either, e.g. '0031'B2 which we all know is an eight bit string
expressed in quat. -John]


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.