On Tue, Oct 17, 2000 at 11:00:35AM +0100, Simon Cozens wrote: > On Tue, Oct 17, 2000 at 10:37:24AM +0100, Simon Cozens wrote: > > What should the tokeniser return for "foo"? > > Uh, tokenizer != lexer. Insert coffee. Yes, writing a tokeniser in a regexp > should be very doable. To allow the lexer to influence the tokeniser, what characters are we going to use in (? ) for smoke and mirrors extensions? (?s) and (?m) are already taken. [Seriously, I was under the impression that the perl tokenizer was influenced by the state of the lexer] Nicholas Clark
- Re: RFC 334 (v1) I'm {STILL} trying to un... Dan Sugalski
- Re: RFC 334 (v1) I'm {STILL} trying to understand... David L. Nicol
- Perl's parser and lexer will likely be in Perl (was Re: RF... Bradley M. Kuhn
- Re: Perl's parser and lexer will likely be in Perl (w... Leon Brocard
- Larry's ALS talk Bradley M. Kuhn
- Re: Larry's ALS talk Jeff Okamoto
- Re: Perl's parser and lexer will likely be in Per... Jeremy Howard
- Re: Perl's parser and lexer will likely be in... Adam Turoff
- Re: Perl's parser and lexer will likely b... Simon Cozens
- Re: Perl's parser and lexer will lik... Simon Cozens
- Re: Perl's parser and lexer will lik... Nicholas Clark
- Re: Perl's parser and lexer will lik... Simon Cozens
- Re: Perl's parser and lexer will lik... John Porter
- Re: Perl's parser and lexer will lik... Dan Sugalski
- Re: Perl's parser and lexer will lik... Ken Fox
- Re: Perl's parser and lexer will lik... Nicholas Clark
- Re: Perl's parser and lexer will lik... Simon Cozens
- Re: Perl's parser and lexer will lik... David L. Nicol
- Re: Perl's parser and lexer will lik... Ken Fox
- Re: Perl's parser and lexer will likely b... Bradley M. Kuhn
- Re: Perl's parser and lexer will lik... Adam Turoff