On Wed, 9 Aug 2000, Bryan C. Warnock wrote: > What I was trying to say, is that I think most of the language RFCs > could be addressed (in one way) by affecting whether and how the parser > interprets what the lexer gives to it. That's closer to the truth, though the RFCs that don't introduce brand new concepts generally affect the runtime behaviour of perl rather than the compile-time behaviour, though some do both. Perl's biggest barrier to doing this is the difficulty of determining what a token is, and that's really what stands in the way. Changing how the parser deals with tokens is reasonably simple compared to that. (Well, as simple as writing parser code) Lexer abuse is needed for things like Python mode, though--without it that's a no go. We may be able to fake it with source filters and parser abuse, though. Dan
- Re: Overloading && || Peter Scott
- Re: Overloading && || Damian Conway
- Re: Overloading && || Damian Conway
- Re: Overloading && || Peter Scott
- Re: Overloading && || Dan Sugalski
- Re: Overloading && || Nick Ing-Simmons
- Re: Overloading && || Nathan Torkington
- Re: Overloading && || Bryan C . Warnock
- Re: Overloading && || Dan Sugalski
- Re: Overloading && || Bryan C . Warnock
- Re: Overloading && || Dan Sugalski
- Re: Overloading && || Chaim Frenkel
- Re: Overloading && || David L. Nicol
- And A Parser In A Pared Tree (was... Bryan C . Warnock
- Re: And A Parser In A Pared Tree ... David L. Nicol
- Re: Overloading && || Damian Conway
- Re: Overloading && || Damian Conway
- Re: Overloading && || Dan Sugalski
- Re: Overloading && || Randal L. Schwartz
- Re: Overloading && || Nathan Torkington
- Re: RFC 49 (v1) Objects should have builtin string SCAL... Nathan Wiger