From: Daniel Hartwig <mandyke@gmail.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] add regexp-split
Date: Fri, 30 Dec 2011 23:23:16 +0800 [thread overview]
Message-ID: <CAN3veRfX2x-WxFdO6Q-veJPOO_G2FwTdqqvN_LuQyYpVFqiy7A@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZofzCdFbjwfEnhu_Q0qSYnMivmoPwk3xHJ-xPHBSvKo55Q@mail.gmail.com>
On 30 December 2011 19:47, Nala Ginrut <nalaginrut@gmail.com> wrote:
> Forget to load (srfi-1 iota) ,again...
>
>
> On Fri, Dec 30, 2011 at 7:40 PM, Nala Ginrut <nalaginrut@gmail.com> wrote:
>>
>> Great! It's better now.
>> Here's the brand new patch~
I notice that this does not handle the case where there are no matches:
scheme@(guile-user)> (regexp-split "[^0-9]" "123")
$26 = ((""))
(let ((ret (fold-matches
regex str (list '() 0 '(""))
becomes:
(let ((ret (fold-matches
regex str (list '() 0 str)
and the result:
scheme@(guile-user)> (regexp-split "[^0-9]" "123")
$28 = ("123")
scheme@(guile-user)> (string-split "123" #\!)
$29 = ("123")
I also note that you are using `substring/shared' when I think you are
after `substring'. Both of these are efficient and use shared memory
when they can, but there is a difference.
next prev parent reply other threads:[~2011-12-30 15:23 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 [this message]
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
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=CAN3veRfX2x-WxFdO6Q-veJPOO_G2FwTdqqvN_LuQyYpVFqiy7A@mail.gmail.com \
--to=mandyke@gmail.com \
--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).