From: Neil Jerram <neil@ossau.homelinux.net>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] add regexp-split
Date: Fri, 30 Dec 2011 16:26:34 +0000 [thread overview]
Message-ID: <87sjk2gh51.fsf@neil-laptop.ossau.uklinux.net> (raw)
In-Reply-To: <CAPjoZocSkvGAcO_Njvn8BDXqehP=RtCkF9EnqBmgrUXpcVC6hw@mail.gmail.com> (Nala Ginrut's message of "Fri, 30 Dec 2011 23:12:34 +0800")
Nala Ginrut <nalaginrut@gmail.com> writes:
> Well, I see.
> So the previous discussion didn't make this proc put into Guile?
> Now that so many people interested in this topic.
I'm afraid I can't recall what happened following that thread.
What feels important to me, though, is the elegance of the overall API.
There are already _some_ regex-related APIs in the core Guile library
(ice-9 regex) and I would guess that there are many many possible
variations of these and other string + regex processing APIs that one
might propose. Also we've now demonstrated that regex-split can be
implemented, on top of the existing library, with only a few lines of
code. Therefore I'd say (speaking only as an observer) that you need to
make a case for how your regex-split beautifully complements what's
already there in (ice-9 regex), or alternatively for replacing (ice-9
regex) with a more beautiful set of operations including regex-split.
Alternatively^2, you could package regex-split outside the core library,
as a test case for the guild hall. Then it doesn't need to be justified
in relation to (ice-9 regex), it can just be a convenient module that
provides a more Python-like API.
Regards,
Neil
next prev parent reply other threads:[~2011-12-30 16:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 9:32 [PATCH] add regexp-split Nala Ginrut
2011-12-29 9:46 ` Nala Ginrut
2011-12-29 10:20 ` Nala Ginrut
2011-12-29 13:58 ` Nala Ginrut
2011-12-30 5:34 ` Daniel Hartwig
2011-12-30 8:46 ` Nala Ginrut
2011-12-30 9:05 ` Nala Ginrut
[not found] ` <CAN3veRdFQyOthFTSLE7v9x3_A4HTPX99DSmDx26dBkeyy=MTDQ@mail.gmail.com>
2011-12-30 9:42 ` Daniel Hartwig
2011-12-30 11:40 ` Nala Ginrut
2011-12-30 11:47 ` Nala Ginrut
2011-12-30 15:23 ` Daniel Hartwig
2011-12-30 10:14 ` Marijn
2011-12-30 10:56 ` Nala Ginrut
2011-12-30 11:48 ` Marijn
2011-12-30 11:52 ` Nala Ginrut
2011-12-30 13:23 ` Marijn
2011-12-30 14:57 ` Daniel Hartwig
2011-12-31 1:46 ` Daniel Hartwig
2011-12-31 2:32 ` Eli Barzilay
2011-12-31 3:16 ` Daniel Hartwig
2011-12-31 3:21 ` Eli Barzilay
2011-12-31 4:37 ` Daniel Hartwig
2011-12-31 7:00 ` Eli Barzilay
2011-12-30 13:03 ` Neil Jerram
2011-12-30 15:12 ` Nala Ginrut
2011-12-30 16:26 ` Neil Jerram [this message]
2011-12-30 16:46 ` Nala Ginrut
2012-01-07 22:44 ` Andy Wingo
2011-12-30 15:33 ` Daniel Hartwig
2011-12-30 15:58 ` Nala Ginrut
-- strict thread matches above, loose matches on Subject: below --
2013-02-01 9:24 Nala Ginrut
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=87sjk2gh51.fsf@neil-laptop.ossau.uklinux.net \
--to=neil@ossau.homelinux.net \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@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).