From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Emacs-like file buffers
Date: Fri, 12 May 2006 21:08:52 -0700 [thread overview]
Message-ID: <87wtcqva5n.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87ejyy8z96.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 13 May 2006 11:55:17 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Rob Browning <rlb@defaultvalue.org> writes:
>> My impression was that Guile just uses whatever library it finds on
>> the system (if any), and that the library found might or might not be
>> POSIX compliant. If that's correct, then I'd much rather have an
>> arrangement where we know exactly what kind of regular expressions
>> Guile will provide on *any* host system.
>
> I'd probably only go so far as help someone link to a decent library,
> a "--with" option on configure or whatever. Non-posix libc would
> probably hurt many programs so you could argue guile needn't try too
> hard to overcome it.
I still think there's quite a lot to be said for the fact that in Perl
(and I assume Python) you can write the equivalent of
(if (regex-match FOO filename)
(rm-rf filename))
and know for *sure* that according to the official documentation
(barring an implementation bug) you will get the exact same behavior
on every supported platform.
Frankly, without some guarantee like that, I would think twice about
trying to write regular expression based, cross-platform scripts (in
particular, destructive programs) using Guile.
Of course if we could add a mandatory, full POSIX regular expression
test suite to make check (whenever regular expressions are available),
then that, along with suitable documentation, would be one way to
solve the problem.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-05-13 4:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 7:18 Emacs-like file buffers Jason Meade
2006-05-07 19:02 ` Rob Browning
2006-05-08 23:42 ` Kevin Ryde
2006-05-09 0:50 ` Rob Browning
2006-05-13 1:55 ` Kevin Ryde
2006-05-13 4:08 ` Rob Browning [this message]
[not found] ` <9c4a82e00605122309g6f3e061etd702479d88664b96@mail.gmail.com>
[not found] ` <87ejyx37af.fsf@trouble.defaultvalue.org>
[not found] ` <9c4a82e00605131824v23a934dah1404210beb57e1b3@mail.gmail.com>
2006-05-14 1:27 ` Fwd: " Jason Meade
2006-05-14 14:58 ` Bruce Korb
2006-05-14 22:34 ` Kevin Ryde
2006-05-14 22:11 ` Kevin Ryde
2006-05-19 12:12 ` Regular expressions 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=87wtcqva5n.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).