From: "Chris K. Jester-Young" <cky944@gmail.com>
To: guile-devel@gnu.org
Subject: Re: regexp-split for Guile
Date: Sun, 21 Oct 2012 15:23:05 -0400 [thread overview]
Message-ID: <20121021192305.GC25831@yarrow> (raw)
In-Reply-To: <CAN3veRcpHN4-WBGyK+bUuCNkeO+oumgvFA1X+mKkY5vYXvdwNA@mail.gmail.com>
On Sun, Oct 21, 2012 at 04:20:09PM +0800, Daniel Hartwig wrote:
> Yes. Keep it simple. Operations like trim-whitespace and
> drop-empty-strings-from-the-result (mentioned in the previous
> discussion) are so easy to do outside of regexp-split, why complicate
> the semantics?
"So easy", but so verbose. We should prefer to make common use cases
easy (and succinct) to use, and not optimise for uncommon ones.
Anyway, in my response to Mark, I mentioned that if we can get
drop-right-while in-tree, we have a middle ground that should make
"everyone" happy. I am against requiring users of regexp-split to
reinvent that wheel each time. Leave the reinvention to Phil Bewig.[1]
Cheers,
Chris.
[1] http://lists.nongnu.org/archive/html/chicken-users/2009-05/msg00024.html
"I never use SRFI-1. My personal standard library has take, drop,
take-while, drop-while, range, iterate, filter, zip, [...]"
next prev parent reply other threads:[~2012-10-21 19:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 14:01 regexp-split for Guile Chris K. Jester-Young
2012-09-17 19:32 ` Thien-Thi Nguyen
2012-09-17 20:06 ` Chris K. Jester-Young
2012-09-18 7:06 ` Sjoerd van Leent Privé
2012-09-18 19:31 ` Chris K. Jester-Young
2012-09-18 19:59 ` Chris K. Jester-Young
2012-10-07 2:38 ` Daniel Hartwig
2012-10-12 21:57 ` Mark H Weaver
2012-10-20 4:01 ` Chris K. Jester-Young
2012-10-20 13:27 ` Mark H Weaver
2012-10-20 14:16 ` Mark H Weaver
2012-10-21 8:20 ` Daniel Hartwig
2012-10-21 19:23 ` Chris K. Jester-Young [this message]
2012-10-21 16:08 ` Chris K. Jester-Young
2012-09-18 12:59 ` nalaginrut
2012-09-18 19:55 ` Chris K. Jester-Young
2012-09-19 0:30 ` nalaginrut
2012-10-04 21:47 ` Ludovic Courtès
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=20121021192305.GC25831@yarrow \
--to=cky944@gmail.com \
--cc=guile-devel@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).