On Tue, Mar 18, 2014 at 4:50 PM, Alessio Stalla <alessiosta...@gmail.com>wrote:
> On Tue, Mar 18, 2014 at 8:54 PM, Paul Tarvydas <paultarvy...@gmail.com>wrote: > >> @All, thanks for the interesting discussion. Certainly gives me >> something to chew on. >> >> Re-reading the responses, I see that, while I did sort-of say it, I >> didn't emphasize the point of this: >> >> I have a PEG-syntax parser written in esrap. >> >> I am binding at least two such parsers as reader-macros (not the normal >> kind of macro). >> > > I always thought that reader macros should be called a different name, > because they are not macros. Yes, they produce code; but that's the only > point they have in common with macros. > Given that that is all that macros do, methinks that a rather comprehensive commonality. Even a keyboard macro has no job other than to take a key chord and produce key strokes, -hp -- Kenneth Tilton Fort Lauderdale, FL http://tiltontec.com http://socialalgebra.com
