Re: What should be check in Lexical Analyzer along with generating tokens?

"Clint Olsen" <clint@0lsen.net>
25 Sep 2002 23:50:30 -0400

          From comp.compilers

Related articles
What should be check in Lexical Analyzer along with generating token vikramasanjeeva@hotmail.com (Vikrama Sanjeeva) (2002-09-14)
Re: What should be check in Lexical Analyzer along with generating t joachim_d@gmx.de (Joachim Durchholz) (2002-09-19)
Re: What should be check in Lexical Analyzer along with generating tok clint@0lsen.net (Clint Olsen) (2002-09-20)
Re: What should be check in Lexical Analyzer along with generating cfc@shell01.TheWorld.com (Chris F Clark) (2002-09-20)
Re: What should be check in Lexical Analyzer along with generating t joachim_d@gmx.de (Joachim Durchholz) (2002-09-22)
Re: What should be check in Lexical Analyzer along with generating clint@0lsen.net (Clint Olsen) (2002-09-25)
Re: What should be check in Lexical Analyzer along with generati clint@0lsen.net (Clint Olsen) (2002-09-29)
Re: What should be check in Lexical Analyzer along with generating tok joachim_d@gmx.de (Joachim Durchholz) (2002-09-29)
Re: What should be check in Lexical Analyzer along with genera joachim_d@gmx.de (Joachim Durchholz) (2002-10-13)
Re: What should be check in Lexical Analyzer along with generating tok lex@cc.gatech.edu (Lex Spoon) (2002-10-18)
Re: What should be check in Lexical Analyzer along with generating t joachim_d@gmx.de (Joachim Durchholz) (2002-10-20)
Re: What should be check in Lexical Analyzer along with generating lars@bearnip.com (Lars Duening) (2002-10-25)
[1 later articles]
| List of all articles for this month |

From: "Clint Olsen" <clint@0lsen.net>
Newsgroups: comp.compilers
Date: 25 Sep 2002 23:50:30 -0400
Organization: AT&T Broadband
References: 02-09-087 02-09-110 02-09-121 02-09-128
Keywords: lex
Posted-Date: 25 Sep 2002 23:50:30 EDT

Joachim Durchholz wrote:


> comment ::= "/*" {token} "*/"
> token ::= comment
> | string | integer | ... (literals)
> | "if" | "then" | ... (keywords)
> | <error>
>
> (The <error> token is meant to be whatever the lexer returns if a
> character sequence is not a legal token.)


Your example does show how the comment would appear in your grammar in
the first place. Comments in most free form languages can appear
_anywhere_ except where they might split tokens (e.g. quoted strings).


-Clint


Post a followup to this message

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