From: Andy Wingo <wingo@pobox.com>
To: Michael Lucy <MichaelGLucy@Gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: PEG Parser
Date: Sat, 29 Jan 2011 12:34:45 +0100 [thread overview]
Message-ID: <m3wrlo3puy.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTimUm_UL9W7EvfoF273U7E7sgOQB8feL-s2=5QfH@mail.gmail.com> (Michael Lucy's message of "Fri, 28 Jan 2011 22:15:15 -0600")
On Sat 29 Jan 2011 05:15, Michael Lucy <MichaelGLucy@Gmail.com> writes:
> Also, macros are notoriously difficult to debug, especially when
> they're generating several hundred lines of code that compiles fine
> but mysteriously produces the wrong result after a seemingly trivial
> change. So porting them from list generation to syntax generation
> turned out to be harder in practice than I had thought it would be.
Hey no worries, you got the thing working in the first place. We'll see
about porting it to use hygienic expansion :)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-01-29 11:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:29 PEG Parser Noah Lavine
2011-01-17 21:32 ` Ludovic Courtès
2011-01-21 15:23 ` Noah Lavine
2011-01-22 21:02 ` Ludovic Courtès
2011-01-24 1:29 ` Noah Lavine
2011-01-24 20:55 ` Ludovic Courtès
2011-01-27 1:40 ` Noah Lavine
2011-01-27 2:23 ` Michael Lucy
2011-01-27 2:38 ` Noah Lavine
2011-01-27 3:02 ` Michael Lucy
2011-01-27 5:17 ` Noah Lavine
2011-01-28 3:25 ` Noah Lavine
2011-01-28 5:13 ` Michael Lucy
2011-01-28 15:48 ` Andy Wingo
2011-01-29 3:07 ` Noah Lavine
2011-01-29 4:15 ` Michael Lucy
2011-01-29 11:34 ` Andy Wingo [this message]
2011-01-29 19:37 ` Noah Lavine
2011-01-30 11:43 ` Andy Wingo
2011-02-02 0:26 ` Noah Lavine
2011-02-06 15:31 ` Noah Lavine
2011-02-18 22:03 ` Andy Wingo
2011-02-23 15:10 ` Noah Lavine
2011-03-04 10:52 ` Andy Wingo
2011-03-04 13:09 ` Noah Lavine
2011-01-29 11:33 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 5:19 Michael Lucy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wrlo3puy.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=MichaelGLucy@Gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).