From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: Michael Lucy <MichaelGLucy@Gmail.com>, guile-devel@gnu.org
Subject: Re: GSOC PEG project
Date: Sat, 17 Jul 2010 14:56:25 +0200 [thread overview]
Message-ID: <878w5a6zd2.fsf@gnu.org> (raw)
In-Reply-To: <m3zkxq1eow.fsf@unquote.localdomain> (Andy Wingo's message of "Sat, 17 Jul 2010 14:21:51 +0200")
Hi,
Andy Wingo <wingo@pobox.com> writes:
> On Sun 11 Jul 2010 09:48, Michael Lucy <MichaelGLucy@Gmail.com> writes:
>
>> On Thu, Jul 8, 2010 at 11:21 AM, Andy Wingo <wingo@pobox.com> wrote:
>>
>>> Humm, another thing to think about: (ice-9 regex) returns "match
>>> structures", which are really just vectors; have a look at them, and if
>>> it makes sense to mimic that interface, re-exporting those accessors
>>> somehow, please do.
>>
>> So, three potential paths from here:
>> 1. Mimic the match structure interface as much as possible.
>> 2. Have a similar but differently-named "peg-match structure"
>> interface that behaves mostly the same but has a few different
>> functions (I think naming them something slightly different would lead
>> to fewer people assuming they worked exactly the same as match
>> structures).
>> 3. Just having a different interface.
>>
>> I'm leaning toward (2); what do other people think? I'd probably:
>> 1. Not have a peg-match:count function at all.
>> 2. Not have the functions take submatch numbers.
>> 3. Have peg-match:substring return the actual substring.
>> 4. Have another function peg-match:parse-tree that returns the parse
>> tree.
>
> Yes, if the needs are different, there's no sense in trying to horn the
> present into the past's shoe. Take the good conventions from (ice-9
> match), but there is no strict need for compatibility.
This should read (ice-9 regex), I think.
Ludo’.
next prev parent reply other threads:[~2010-07-17 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 6:05 GSOC PEG project Michael Lucy
2010-07-05 22:40 ` Ludovic Courtès
2010-07-05 23:59 ` Michael Lucy
2010-07-06 1:41 ` No Itisnt
2010-07-06 21:37 ` Ludovic Courtès
2010-07-08 16:23 ` Andy Wingo
2010-07-08 16:21 ` Andy Wingo
2010-07-11 7:48 ` Michael Lucy
2010-07-17 12:21 ` Andy Wingo
2010-07-17 12:56 ` Ludovic Courtès [this message]
2010-07-18 11:57 ` Andy Wingo
2010-07-08 10:29 ` Andy Wingo
2010-07-09 7:58 ` Michael Lucy
2010-07-10 9:49 ` Michael Lucy
2010-07-17 12:19 ` Andy Wingo
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=878w5a6zd2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=MichaelGLucy@Gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).