From: "Wolfgang Jährling" <wolfgang@pro-linux.de>
Cc: bug-guile@gnu.org, guile-user@gnu.org
Subject: Re: regexp-exec fails for long strings
Date: Wed, 15 May 2002 08:04:20 +0200 [thread overview]
Message-ID: <20020515080420.B201@dose.pro-linux.de> (raw)
In-Reply-To: <E177prI-0001VF-00@giblet>; from ttn@giblet.glug.org on Tue, May 14, 2002 at 08:53:48PM -0700
Thien-Thi Nguyen <ttn@giblet.glug.org> wrote:
> From: Thien-Thi Nguyen <ttn@giblet.glug.org>
> Date: Thu, 25 Apr 2002 16:29:40 -0700
>
> i traced this to `regexec' (glibc 2.2.4) and stopped -- it's not a guile
> bug after all, as far as i could tell. (also, could not reproduce the
> behavior under FreeBSD 4.4-RELEASE.)
>
> probably time to apt-get update...
>
> this problem persists w/ glibc 2.2.5. hmmm....
AFAIK, the glibc-people are rewriting the regex code for 2.3, because
the current implementation got unmaintainable and has various strange
limitations. This could be one of those.
Cheers,
GNU/Wolfgang
--
Wolfgang Jährling <wolfgang@pro-linux.de> \\ http://stdio.cjb.net/
Debian GNU/Hurd user && Debian GNU/Linux user \\ http://www.gnu.org/
The Hurd Hacking Guide: http://www.gnu.org/software/hurd/hacking-guide/
["We're way ahead of you here. The Hurd has always been on the ]
[ cutting edge of not being good for anything." -- Roland McGrath ]
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-05-15 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 20:05 regexp-exec fails for long strings Thien-Thi Nguyen
2002-04-25 21:47 ` rm
2002-04-25 23:29 ` Thien-Thi Nguyen
2002-05-15 3:53 ` Thien-Thi Nguyen
2002-05-15 6:04 ` Wolfgang Jährling [this message]
2002-05-15 8:19 ` Thien-Thi Nguyen
2002-04-26 4:32 ` Tom Lord
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=20020515080420.B201@dose.pro-linux.de \
--to=wolfgang@pro-linux.de \
--cc=bug-guile@gnu.org \
--cc=guile-user@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).