Re: problems with identifiers and keywords...

nmm1@cus.cam.ac.uk (Nick Maclaren)
19 Nov 2004 00:47:34 -0500

          From comp.compilers

Related articles
[9 earlier articles]
Re: problems with identifiers and keywords... cfc@shell01.TheWorld.com (Chris F Clark) (2004-11-14)
Re: problems with identifiers and keywords... genew@mail.ocis.net (Gene Wirchenko) (2004-11-14)
Re: problems with identifiers and keywords... gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-11-17)
Re: problems with identifiers and keywords... gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-11-17)
Re: problems with identifiers and keywords... lkrupp@pssw.NOSPAM.com.INVALID (Louis Krupp) (2004-11-17)
Re: problems with identifiers and keywords... cfc@shell01.TheWorld.com (Chris F Clark) (2004-11-17)
Re: problems with identifiers and keywords... nmm1@cus.cam.ac.uk (2004-11-19)
Re: problems with identifiers and keywords... gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-11-19)
Re: problems with identifiers and keywords... gracjan@acchsh.nospam.com (Gracjan Polak) (2004-11-19)
Re: problems with identifiers and keywords... Martin.Ward@durham.ac.uk (Martin Ward) (2004-11-19)
Re: problems with identifiers and keywords... Peter_Flass@Yahoo.com (Peter Flass) (2004-11-20)
Re: problems with identifiers and keywords... genew@mail.ocis.net (Gene Wirchenko) (2004-11-20)
Re: problems with identifiers and keywords... david.thompson1@worldnet.att.net (Dave Thompson) (2004-11-28)
[5 later articles]
| List of all articles for this month |
From: nmm1@cus.cam.ac.uk (Nick Maclaren)
Newsgroups: comp.compilers
Date: 19 Nov 2004 00:47:34 -0500
Organization: University of Cambridge, England
References: 04-10-148 04-10-170 04-10-174 04-11-008 04-11-011 04-11-032
Keywords: parse, design
Posted-Date: 19 Nov 2004 00:47:34 EST



|> >Another problem is that many compilers aren't good at giving a
|> >meaningful diagnostic when a keyword is used as an identifier.


My experience is that is due to one of two causes:


        The language's syntax is a mess (e.g. Fortran or C), or is too
clever by half (Algol 68).


        The compiler uses the theoretical parsing methods, as taught to
undergraduates.


In both cases, the root cause is the failure to include diagnosis and
error handling as part of the design. I have seen:


End of statement was expected but end of statement found (Fortran).


Invalid program [the sole diagnostic] (Algol 68)


Bracket mismatch [at end of file] (C).


I regret to say that I can't see a joke in that :-(


Regards,
Nick Maclaren.


Post a followup to this message

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