unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: PEG Patches
Date: Fri, 25 Mar 2011 19:06:07 +0100	[thread overview]
Message-ID: <m3lj03f52o.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTikhi4Emq730utYgh7FZTCfKYyzh3nV7ydoS2jYv@mail.gmail.com> (Noah Lavine's message of "Sun, 6 Mar 2011 00:25:13 -0500")

On Sun 06 Mar 2011 06:25, Noah Lavine <noah.b.lavine@gmail.com> writes:

> Attached is a series of patches I've made for the wip-mlucy branch. It
> splits the PEG code into several little modules which go in
> module/ice-9/peg/. The original peg source file becomes very little.
> At the end it finally loses its big eval-when wrapper.

Cool!  These cleanups are great.

However... when you added the files, you did not add them to
Makefile.am, so they don't get built.  I went back to add them, but they
don't compile, and it's because of the circularity we have discussed in
other threads.

I think the solution is to confront the circularity directly.  It exists
because the PEG s-exp grammar also deals with the string grammar, which
needs an already-build PEG parser.

Let's break it instead into layers without cycles: removing the string
grammar from the s-exp code generator.  If we want a layer with both, we
build it on top of the two lower layers.

What do you think?

Andy
-- 
http://wingolog.org/



  parent reply	other threads:[~2011-03-25 18:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06  5:25 PEG Patches Noah Lavine
2011-03-07  1:28 ` Noah Lavine
2011-03-25 18:06 ` Andy Wingo [this message]
2011-03-28 20:44   ` Noah Lavine
2011-03-28 20:46     ` Noah Lavine
2011-03-28 22:17     ` Michael Lucy
2011-03-29  8:00     ` Andy Wingo
2011-03-29 12:47       ` Noah Lavine
2011-03-29 13:20         ` Andy Wingo
2011-03-31 21:48           ` Noah Lavine

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=m3lj03f52o.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    /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).