unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Emacs-like file buffers
Date: Mon, 08 May 2006 17:50:23 -0700	[thread overview]
Message-ID: <874q00xbqo.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <871wv4nkx7.fsf@zip.com.au> (Kevin Ryde's message of "Tue, 09 May 2006 09:42:12 +1000")

Kevin Ryde <user42@zip.com.au> writes:

> Rob Browning <rlb@defaultvalue.org> writes:
>>
>> I would really like to see Guile provide a fixed regular expression
>> format, one that doesn't vary depending on what the build platform has
>> available.  Without that, you cannot write scripts that are portable,
>> at least not with respect to regular expressions.
>
> If you assume you've got mostly posix then it's not too bad is it?

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.

As motivation, imagine you're using Guile to write a cross-platform
tool that will need to use regular expressions to build a list of
files to pass to the equivalent of "rm -rf".

>>     POSIX, Emacs, Perl?
>
> The perl way has its fans.  I guess an add-on that let you get that
> instead or as well as the basic posix bits might be cute.

A while back I actually hacked up a preliminary (use-modules (pcre)).
(I probably still have the source around here somewhere.)

>>   - Is it acceptable to add an external dependency for regular
>>     expression suppport,
>
> It might have to be LGPL to maintain that status on the resulting
> program.

Right, though the main concern I was trying to raise was that, as it
stands now, Guile has very few external dependencies, and so we should
probably consider carefully the merit of adding any given new
dependency.

-- 
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


  reply	other threads:[~2006-05-09  0:50 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 [this message]
2006-05-13  1:55       ` Kevin Ryde
2006-05-13  4:08         ` Rob Browning
     [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=874q00xbqo.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@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).