From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Gregory Marton <gremio@mit.edu>
Cc: bug-guile@gnu.org
Subject: Re: [bug #20056] guile 1.8.1 regular expressions die on #nul (character zero) in operand
Date: Mon, 04 Jun 2007 19:43:04 +0200 [thread overview]
Message-ID: <87hcpnlion.fsf@ambire.localdomain> (raw)
In-Reply-To: <20070603-012934.sv59778.51980@savannah.gnu.org> (Gregory Marton's message of "Sun\, 03 Jun 2007 01\:29\:35 +0000")
() Gregory Marton <INVALID.NOREPLY@gnu.org>
() Sun, 03 Jun 2007 01:29:35 +0000
This used to work in guile 1.3.4 but I haven't
checked the versions in between.
data point:
guile> (version)
"1.4.1.107.9.0.7"
guile> (regexp-exec (make-regexp ".") (string #\nul))
#f
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2007-06-04 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 1:29 [bug #20056] guile 1.8.1 regular expressions die on #nul (character zero) in operand Gregory Marton
2007-06-04 17:43 ` Thien-Thi Nguyen [this message]
2007-06-05 8:01 ` Ludovic Courtès
2007-06-05 10:14 ` Gregory Marton
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=87hcpnlion.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=bug-guile@gnu.org \
--cc=gremio@mit.edu \
/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).