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

"Lex Spoon" <lex@cc.gatech.edu>
18 Oct 2002 23:22:50 -0400

          From comp.compilers

Related articles
[2 earlier articles]
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 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)
Re: What should be check in Lexical Analyzer along with generating lex@cc.gatech.edu (Lex Spoon) (2002-10-25)
| List of all articles for this month |

From: "Lex Spoon" <lex@cc.gatech.edu>
Newsgroups: comp.compilers
Date: 18 Oct 2002 23:22:50 -0400
Organization: Georgia Institute of Technology
References: 02-09-087 02-09-110 02-09-121 02-09-128 02-09-141 02-09-156 02-10-010
Keywords: lex
Posted-Date: 18 Oct 2002 23:22:50 EDT

"Joachim Durchholz" <joachim_d@gmx.de> writes:


> Clint Olsen wrote:
> >
> > /* parse !$#%$# this! :) */
> >
> > I don't see how by your example the above snippet would work.
>
> The expletive would probably go into the <error> token. Which is there
> exactly for the purpose of parsing stuff that the scanner doesn't like.


Here's a harder example:




/* parse "this */ 10 /* and this" */




It will scan as four tokens:


      /*
      parse
      "this */ 10 /* and this"
      */




The parser will be in trouble now if it wants to pull out the "10".
Thus, you seem to need a special scanner state to handle the meat of a
comment.


-Lex


Post a followup to this message

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