Re: Languages that are hard to parse

Tony Finch <dot@dotat.at>
24 May 2005 10:17:44 -0400

          From comp.compilers

Related articles
[5 earlier articles]
Re: Languages that are hard to parse gah@ugcs.caltech.edu (glen herrmannsfeldt) (2005-05-20)
Re: Languages that are hard to parse DrDiettrich@compuserve.de (Hans-Peter Diettrich) (2005-05-20)
Re: Languages that are hard to parse henry@spsystems.net (2005-05-21)
Re: Languages that are hard to parse gah@ugcs.caltech.edu (glen herrmannsfeldt) (2005-05-22)
Re: Languages that are hard to parse Satyam@satyam.com.ar (Satyam) (2005-05-22)
Re: Languages that are hard to parse DrDiettrich@compuserve.de (Hans-Peter Diettrich) (2005-05-22)
Re: Languages that are hard to parse dot@dotat.at (Tony Finch) (2005-05-24)
Re: Languages that are hard to parse wclodius@lanl.gov (2005-05-24)
Re: Languages that are hard to parse Martin.Ward@durham.ac.uk (Martin Ward) (2005-05-24)
Re: Languages that are hard to parse ralph@inputplus.co.uk (2005-05-26)
Re: Languages that are hard to parse hannah@schlund.de (2005-06-02)
Re: Languages that are hard to parse zvr@pobox.com (Alexios Zavras) (2005-06-02)
Re: Languages that are hard to parse gene@abhost.us (Gene Wirchenko) (2005-06-04)
| List of all articles for this month |

From: Tony Finch <dot@dotat.at>
Newsgroups: comp.compilers
Date: 24 May 2005 10:17:44 -0400
Organization: dotat labs
References: 05-05-119 05-05-182 05-05-192 05-05-200
Keywords: parse, design

Hans-Peter Diettrich <DrDiettrich@compuserve.de> wrote:
>Okay, I didn't realize the problems resulting from a huge number of
>keywords. OTOH languages with few keywords, like C, can come with a
>huge library, containing "predefined" words. Is it really easier to
>remember the symbols defined in every #included header file, and if so
>- why?
>
>[I think that C's library names are easier to deal with than COBOL
>reserved words because you only need to be aware of the names in the
>libraries you use, while in COBOL you have to avoid reserved words
>even from parts of the language that you don't know and never
>use. -John]


In addition to that, the compiler error message from a conflicting
declaration is likely to be more helpful than a syntax error arising
from a misplaced keyword. The declaration probably doesn't even count
as conflicting if it occurs within an inner scope - though in C you
can break that advantage of libraries by defining macros in your
headers.


Tony.
--
f.a.n.finch <dot@dotat.at> http://dotat.at/
WEST NORTHERN SECTION: NORTH OR NORTHEAST 4 OR 5, INCREASING 6 FOR A TIME.
MAINLY FAIR. GOOD.


Post a followup to this message

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