From: Tom Lord <lord@regexps.com>
Cc: ttn@glug.org, bug-guile@gnu.org, guile-user@gnu.org
Subject: Re: regexp-exec fails for long strings
Date: Thu, 25 Apr 2002 21:32:01 -0700 (PDT) [thread overview]
Message-ID: <aaal5k$b5t$2@main.gmane.org> (raw)
In-Reply-To: <20020425214713.GA19857@www> (rm@fabula.de)
Hmmm, never really used guile's regex heavily - that's where i
still use <blush>perl</blush>.
If you want high-power regexps, you should resurrect the Rx interface,
grabbing the latest libhackerlab. In fact, rather than resurrecting
the old Guile Rx interface, you should grab and adapt the one from
systas (not currently in release, but I'll put up a new version soon).
I regularly use regexps that are several KB long, constructed by a
structured regexp compiler similar to the one in SCSH. It's fast,
convenient, and very accurate.
-t
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-04-26 4:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E170pV0-00018q-00@giblet>
2002-04-25 21:47 ` regexp-exec fails for long strings rm
[not found] ` <20020425214713.GA19857@www>
2002-04-25 23:14 ` Wolfgang Jährling
2002-04-25 23:29 ` Thien-Thi Nguyen
2002-04-26 4:32 ` Tom Lord [this message]
[not found] ` <E170sgG-0001Na-00@giblet>
2002-05-15 3:53 ` Thien-Thi Nguyen
[not found] ` <E177prI-0001VF-00@giblet>
2002-05-15 6:04 ` Wolfgang Jährling
[not found] ` <20020515080420.B201@dose.pro-linux.de>
2002-05-15 8:19 ` Thien-Thi Nguyen
2002-04-25 20:05 Thien-Thi Nguyen
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='aaal5k$b5t$2@main.gmane.org' \
--to=lord@regexps.com \
--cc=bug-guile@gnu.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).