From: Andy Wingo <wingo@pobox.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: add regexp-split: a summary and new proposal
Date: Sun, 08 Jan 2012 00:05:03 +0100 [thread overview]
Message-ID: <87ipknf71c.fsf@pobox.com> (raw)
In-Reply-To: <CAN3veRcgnoRN3XdfSrF_=T1Aq6DZ_kQMpV6T8AG46X=EPNanGw@mail.gmail.com> (Daniel Hartwig's message of "Sat, 31 Dec 2011 13:54:31 +0800")
On Sat 31 Dec 2011 06:54, Daniel Hartwig <mandyke@gmail.com> writes:
> An attempt to summarize the pertinent points of the thread [1].
>
> [1]
> http://lists.gnu.org/archive/html/guile-devel/2011-12/msg00241.html
Thanks for doing this! I replied earlier without having read this
thread. Sorry for being a serial processor :)
> * [Vanilla `string-split' expanded to support the CHAR_PRED
> semantics of `string-index' et al.]
Makes sense to me.
> * New function `string-explode' similar to `string-split' but returns
> the deliminators in it's result.
"delimiters" :) Also, "Explode" has a meaning in the PHP world like our
"split", but oh well. I would be OK with this.
> * Regex module replaces both of these with regexp-enhanced versions.
Sure. I like Eli's suggestion of having the delimiters be the full set
of matching groups, as a list, but perhaps this could be controlled by a
keyword argument.
MHO at least :)
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-01-07 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 5:54 add regexp-split: a summary and new proposal Daniel Hartwig
2011-12-31 7:30 ` Eli Barzilay
2011-12-31 9:30 ` Daniel Hartwig
2011-12-31 21:13 ` Eli Barzilay
2012-01-07 23:05 ` Andy Wingo [this message]
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=87ipknf71c.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mandyke@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).