On Fri, Aug 04, 2000 at 01:18:36PM -0400, John Porter wrote: > O.k., what I really meant was, When they're both incapable of doing > the sorts of things I want a macro language to do, does it matter > that one is gobs more powerful than the other? I freely admit to knowing very little about macro languages other than m4 and cpp; if you've got a set of features that you think would be better it'd make grist for an RFC. There seems to be moderate sentiment for a macro language and no strong opposition, go for it.
- Re: Recording what we decided *not* to do, and why Peter Scott
- Re: Recording what we decided *not* to do, and why Michael Mathews
- Re: Recording what we decided *not* to do, and why John Porter
- Re: Recording what we decided *not* to do, and why Johan Vromans
- Re: Recording what we decided *not* to do, and why Tom Christiansen
- Re: Recording what we decided *not* to do, and why John Porter
- Re: Recording what we decided *not* to do, and why Steve Simmons
- Re: Recording what we decided *not* to do, and why John Porter
- Re: Recording what we decided *not* to do, and why Tom Christiansen
- Re: Recording what we decided *not* to do, and why John Porter
- Re: Recording what we decided *not* to do, and why Steve Simmons
- Re: Recording what we decided *not* to do, and why Jonathan Scott Duff
- Proto-RFC: A Standard Always-Live Preprocessor John Porter
- Re: Proto-RFC: A Standard Always-Live Preprocessor Dan Sugalski
- Re: Recording what we decided *not* to do, and why Russ Allbery
- Preprocessing (Was: Re: Recording what we decided *not... Johan Vromans
- Re: Preprocessing (Was: Re: Recording what we decided ... Russ Allbery
- Re: Recording what we decided *not* to do, and why Johan Vromans
- Re: Recording what we decided *not* to do, and why Glenn Linderman
- Re: Recording what we decided *not* to do, and why Tom Christiansen
- Re: Recording what we decided *not* to do, and why Johan Vromans