Re: Language used to write compilers

vbdis@aol.com (VBDis)
9 Jan 2005 20:50:51 -0500

          From comp.compilers
Related articles
[9 earlier articles]
Re: Language used to write compilers nmm1@cus.cam.ac.uk (2004-12-31)
Re: Language used to write compilers nmm1@cus.cam.ac.uk (2004-12-31)
Re: Language used to write compilers idbaxter@semdesigns.com (Ira Baxter) (2004-12-31)
Re: Language used to write compilers Peter_Flass@Yahoo.com (Peter Flass) (2005-01-01)
Re: Language used to write compilers nmm1@cus.cam.ac.uk (2005-01-03)
Re: Language used to write compilers napi@cs.indiana.edu (2005-01-03)
Re: Language used to write compilers vbdis@aol.com (2005-01-09)
Re: Language used to write compilers nmm1@cus.cam.ac.uk (2005-01-12)
| List of all articles for this month |
From: vbdis@aol.com (VBDis)
Newsgroups: comp.compilers
Date: 9 Jan 2005 20:50:51 -0500
Organization: AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com
References: 04-12-158
Keywords: practice
Posted-Date: 09 Jan 2005 20:50:51 EST

Im Artikel 04-12-158, nmm1@cus.cam.ac.uk (Nick Maclaren)
schreibt:


>Slightly off-topic, but indicative, is the fact that almost no
>compilers identify the line for both ends of a bracketting mismatch.


Where would that make sense? An opening bracket too much is mismatched
at EOF, and a closing bracket too much is mismatched at BOF?


DoDi
[There's more than one kind of bracket. If the parser sees a close
paren when it's expecting a close brace, that's an error. Perl tells
you where the open whatever was, and it's handy. -John]


Post a followup to this message

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