Adam Turoff wrote: > to write the Perl tokenizer in a Perl[56] regex, which is more easily > parsable in C. All of a sudden, toke.c is replaced by toke.re, which > would be much more legible to this community (which is more of a strike > against toke.c instead of a benefit of some toke.re). Larry brought this up in his talk. Of course, I believe that Larry was sleep-deprived at the time, too. ;) > It was late though. Might have been sleep deprevation talking. -- Bradley M. Kuhn - http://www.ebb.org/bkuhn
- 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