John Porter <[EMAIL PROTECTED]> writes: > But a standardized macro facility would be nice. Although -- > wouldn't it have to parse perl? Or else have a wholly distinct > grammar? Several macro processors exist and are easily available. I do not see the need to duplicate (parts of) their functionality in perl. Personally, I'd even trow out -P. -- Johan
- Re: Recording what we decided *not* to do, and why Steve Simmons
- Re: Recording what we decided *not* to do, and wh... Michael Mathews
- Re: Recording what we decided *not* to do, an... Jonathan Scott Duff
- Re: Recording what we decided *not* to do... Michael Mathews
- Re: Recording what we decided *not* t... Jonathan Scott Duff
- Re: Recording what we decided *not* t... John Porter
- Re: Recording what we decided *n... Larry Wall
- Re: Recording what we decided *n... Peter Scott
- Re: Recording what we decided *n... Michael Mathews
- Re: Recording what we decided *n... John Porter
- Re: Recording what we decided *n... Johan Vromans
- Re: Recording what we decided *n... Tom Christiansen
- Re: Recording what we decided *n... John Porter
- Re: Recording what we decided *n... Steve Simmons
- Re: Recording what we decided *n... John Porter
- Re: Recording what we decided *n... Tom Christiansen
- Re: Recording what we decided *n... John Porter
- Re: Recording what we decided *n... Steve Simmons
- Re: Recording what we decided *n... Jonathan Scott Duff
- Proto-RFC: A Standard Always-Liv... John Porter
- Re: Proto-RFC: A Standard Always... Dan Sugalski