From: tomas@tuxteam.de
To: Wojciech Meyer <wojciech.meyer@googlemail.com>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Structural regular expressions
Date: Sat, 11 Sep 2010 10:33:18 +0200 [thread overview]
Message-ID: <20100911083318.GA10266@tomas> (raw)
In-Reply-To: <87pqwkyann.fsf@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Sep 11, 2010 at 08:58:04AM +0100, Wojciech Meyer wrote:
> Miles Bader <miles@gnu.org> writes:
>
> > "Drew Adams" <drew.adams@Oracle.Com> writes:
> >> That's the real point, I believe: the paper touts the use of regexps
> >> to divide text into chunks that match - chunks that are not
> >> necessarily lines, in order to then act on those chunks in some way.
> >
> > Not a good base, I think -- regexps are not really powerful enough to do
> > the job well.
>
> Yes regexp are quite limited.
> Maybe a simple PEG parser based on packrat, with a syntax sugar for
> defining one line set of rules?
While PEG is interesting in itself (and I think Emacs should have
something like that, just to test its strengths/weaknesses wrt regex), I
think Drew is right: A way, *any* way to define a "buffer subset", maybe
partitioned into "chunks" is useful here. So at this level, I'd think
concentrating on interface design (user & programmer) makes most sense,
abstracting from possible implementations (regex, peg, font-lock,
hand-built parser).
The (possible) implementations should (I think) just guide the design of
the interfaces (as examples). In the ideal case, it should be possible
to use whatever implementation is most helpful (or combine them: union,
intersection, symmetric difference).
Just dreaming?
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFMiz7OBcgs9XrR2kYRAjZvAJ9Hzc4Dk2Z4t3wohMQJX/8544MvIQCffrxr
WKNM0E3e/fJ3UF61J4Ez7c4=
=tDCG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-09-11 8:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 19:25 Structural regular expressions Tom
2010-09-07 20:08 ` Lennart Borgman
2010-09-07 20:27 ` Tom
2010-09-07 21:08 ` Lennart Borgman
2010-09-08 1:13 ` Eric Schulte
2010-09-08 8:46 ` Stefan Monnier
2010-09-08 9:20 ` Lawrence Mitchell
2010-09-08 10:30 ` Kan-Ru Chen
2010-09-09 6:34 ` Harald Hanche-Olsen
2010-09-08 14:29 ` Stefan Monnier
2010-09-08 15:52 ` Lawrence Mitchell
2010-09-08 22:46 ` Stefan Monnier
2010-09-09 7:07 ` David Kastrup
2010-09-09 17:03 ` Stefan Monnier
2010-09-10 12:23 ` David Kastrup
2010-09-10 13:31 ` Stefan Monnier
2010-09-09 20:47 ` Davis Herring
2010-09-09 22:52 ` Lennart Borgman
2010-09-10 10:48 ` Stefan Monnier
2010-09-10 15:43 ` Richard Stallman
2010-09-10 17:03 ` David House
[not found] ` <AANLkTi=dv8n40x-rTtz@mail.gmail.com>
2010-09-10 20:29 ` Tom
2010-09-10 23:50 ` Drew Adams
2010-09-11 2:23 ` Miles Bader
2010-09-11 7:44 ` Tom
2010-09-11 7:58 ` Wojciech Meyer
2010-09-11 8:33 ` tomas [this message]
2010-09-11 15:04 ` Drew Adams
2010-09-11 15:49 ` Richard Stallman
2010-09-12 13:48 ` Stefan Monnier
2010-09-12 14:09 ` Lennart Borgman
2010-09-12 16:43 ` Drew Adams
2010-09-12 17:03 ` Lennart Borgman
2010-09-12 21:31 ` Drew Adams
2010-09-09 15:51 ` Tom
2010-09-09 16:01 ` Lennart Borgman
2010-09-09 16:23 ` Tom
2010-09-09 16:44 ` Lennart Borgman
2010-09-09 16:53 ` Tom
2010-09-09 17:02 ` Lennart Borgman
2010-09-09 19:27 ` Daniel Colascione
2010-09-08 0:00 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100911083318.GA10266@tomas \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=wojciech.meyer@googlemail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.