Simon Cozens wrote: > This would have to take account of the fact that Perl's tokeniser is > aware of what's going on in the rest of perl. Consider > > print foo; > > What should the tokeniser return for "foo"? Is it a bareword? Is it a > subroutine call? Is it a class? Is it - heaven forbid - a filehandle? > Well, it could be any of these things. You have to choose. No you don't. The decision of what to make of this bareword can be deferred.
- Re: Perl's parser and lexer will likely be in Perl (was Re... Adam Turoff
- Re: Perl's parser and lexer will likely be in Perl (w... Simon Cozens
- Re: Perl's parser and lexer will likely be in Per... Simon Cozens
- Re: Perl's parser and lexer will likely be in Per... Nicholas Clark
- Re: Perl's parser and lexer will likely be in Per... Simon Cozens
- Re: Perl's parser and lexer will likely be in Per... John Porter
- Re: Perl's parser and lexer will likely be in Per... Dan Sugalski
- Re: Perl's parser and lexer will likely be in Per... Ken Fox
- Re: Perl's parser and lexer will likely be in Per... Nicholas Clark
- Re: Perl's parser and lexer will likely be in Per... Simon Cozens
- Re: Perl's parser and lexer will likely be in Per... David L. Nicol
- Re: Perl's parser and lexer will likely be in Per... Ken Fox
- Re: Perl's parser and lexer will likely be in Perl (w... Bradley M. Kuhn
- Re: Perl's parser and lexer will likely be in Per... Adam Turoff
- Re: Perl's parser and lexer will likely be in Per... Dan Sugalski
- Re: Perl's parser and lexer will likely be in Per... Adam Turoff
- Re: Perl's parser and lexer will likely be in Perl (was Re... Dan Sugalski