Related articles |
---|
Using Bison and Delphi mikehahn@rogers.com (Mike Hahn) (2004-11-17) |
Re: Using Bison and Delphi vbdis@aol.com (2004-11-19) |
Re: Using Bison and Delphi mikehahn@rogers.com (Mike Hahn) (2004-11-20) |
Re: Using Bison and Delphi vbdis@aol.com (2004-11-26) |
Re: Using Bison and Delphi vbdis@aol.com (2004-11-28) |
Re: Using Bison and Delphi jeremy.wright@microfocus.com (Jeremy Wright) (2004-11-28) |
Re: Using Bison and Delphi mikehahn@rogers.com (Mike Hahn) (2004-12-05) |
Re: Using Bison and Delphi strohm@airmail.net (John R. Strohm) (2004-12-06) |
From: | vbdis@aol.com (VBDis) |
Newsgroups: | comp.compilers |
Date: | 28 Nov 2004 23:19:41 -0500 |
Organization: | AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com |
References: | 04-11-078 |
Keywords: | Pascal, syntax, design |
Posted-Date: | 28 Nov 2004 23:19:41 EST |
Im Artikel 04-11-078, "Mike Hahn" <mikehahn@rogers.com>
schreibt:
>I disagree that the omission of the Java dot operator (making it
>implied) is a language flaw. If the first token (at the statement
>level) is an identifier, then the parser knows that a procedure call
>is coming. If the first token (at the expression level) is an
>identifier, then the parser knows that a function call is
>coming.
Does your language happen to have variables, too?
= foo bar oops;
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.