unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Emacs-like file buffers
Date: Sat, 13 May 2006 11:55:17 +1000	[thread overview]
Message-ID: <87ejyy8z96.fsf@zip.com.au> (raw)
In-Reply-To: 874q00xbqo.fsf@trouble.defaultvalue.org

Rob Browning <rlb@defaultvalue.org> writes:
>
>   - How is the addition of support for Unicode likely to affect any
>     regular expression or buffer work?

Oh, I see what you mean.  Yes, no doubt a utf-8 aware regexp library
would be needed.

To turn around what I said about glibc, glibc in the right setlocale
does it, but I think it'd depend on having and finding a utf-8 locale
that's been enabled in locale.gen (or wherever).  Switching back and
forward with setlocale would no doubt be as horrible as the same thing
we do with tzset, though when I measured it setlocale was pretty fast
(unlike tzset).

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

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

That sounds good as an add-on.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-05-13  1:55 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 [this message]
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=87ejyy8z96.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --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).