unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Jason Meade" <jemeade@gmail.com>
Cc: guile-devel@gnu.org
Subject: Fwd: Emacs-like file buffers
Date: Sat, 13 May 2006 18:27:14 -0700	[thread overview]
Message-ID: <9c4a82e00605131827h16d7dad5l59848987406707b1@mail.gmail.com> (raw)
In-Reply-To: <9c4a82e00605131824v23a934dah1404210beb57e1b3@mail.gmail.com>

On 5/13/06, Rob Browning <rlb@defaultvalue.org> wrote:
> "Jason Meade" <jemeade@gmail.com> writes:
>
> > Since Perl's source is available, why not just grab its regex engine
> > and drop it into guile? If that's no good for licensing or other
> > reasons, then there's always PCRE (http://www.pcre.org/).
>
> Either of those would be a possibility, but first we'd have to come to
> a decision about whether or not we wanted Guile's official regular
> expressions to be Perl format.

...

>
> And of course there are also arguments in favor of the other formats
> (POSIX or Emacs).  I'm OK with any of them; I'd just like to have a
> standard.
>

~~ *sigh!* I forgot to cc the group... :( ~~

Is there a standard for regular expressions somewhere? It seems like
most implements (from grep through tcl, perl, and beyond) seem to
agree on simple stuff like ^[a-c]?002*[^b]+$ etc... (not all
understand ? and + I've noticed....) but very few seem to share an
affinity for \w or \< ... \> etcetera.

I don't use regular expressions (outside of grep) everyday, but when I
do use them, it's usually for some serious pattern matching, with
variable capture (via $1, or \#1 etc). I'm starting to incorporate
search-forward and search-backwards into my filebuffer lib. For that
kind of work, even strchr will work (sorta. binary data is a problem).
However, eventually I'll want to be able to regex my buffers, and once
I add the guile hooks, it would be nice to share the same regex syntax
with everyone else. After all, the last thing you want is to load a
module, only to find that it's not syntax compatible with the rest of
the language!

-Jason


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


  parent reply	other threads:[~2006-05-14  1:27 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
     [not found]           ` <9c4a82e00605122309g6f3e061etd702479d88664b96@mail.gmail.com>
     [not found]             ` <87ejyx37af.fsf@trouble.defaultvalue.org>
     [not found]               ` <9c4a82e00605131824v23a934dah1404210beb57e1b3@mail.gmail.com>
2006-05-14  1:27                 ` Jason Meade [this message]
2006-05-14 14:58                   ` Fwd: " 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=9c4a82e00605131827h16d7dad5l59848987406707b1@mail.gmail.com \
    --to=jemeade@gmail.com \
    --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).