From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] plan 9 regexp
Date: Sun, 7 Jun 2009 13:11:57 -0400 [thread overview]
Message-ID: <5484a4d7541fb835580f09a1448bc9d9@quanstro.net> (raw)
In-Reply-To: <20090606135550.60993bda.ori@eigenstate.org>
On Sun Jun 7 11:02:51 EDT 2009, ori@eigenstate.org wrote:
> On Thu, 4 Jun 2009 20:05:01 -0400
> Dan Cross <crossd@gmail.com> wrote:
>
>
> > I'm sure. This is something that I would be interested in revisiting;
> > do you have any pointers to particularly relevant information? I
> > wonder how nicely these tree automata could be packaged into an
> > awk-like form.
> >
> > - Dan C.
>
> Look up iburg and twig. They're tree pattern matchers that could be
> adapted to do what you want, although they're more like yacc than awk.
i'm surprised that no one has mentiond http://pdos.csail.mit.edu/xoc/
by russ et al.
- erik
next prev parent reply other threads:[~2009-06-07 17:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 23:41 Francisco J Ballesteros
2009-06-03 23:56 ` erik quanstrom
2009-06-04 1:22 ` J.R. Mauro
2009-06-04 11:43 ` Martin Neubauer
2009-06-04 19:23 ` J. R. Mauro
2009-06-04 19:27 ` erik quanstrom
2009-06-04 21:54 ` J.R. Mauro
2009-06-05 18:12 ` erik quanstrom
2009-06-13 18:29 ` J.R. Mauro
2009-06-04 21:35 ` Dan Cross
2009-06-04 22:36 ` Charles Forsyth
2009-06-05 0:05 ` Dan Cross
2009-06-06 17:55 ` Ori Bernstein
2009-06-07 17:11 ` erik quanstrom [this message]
2009-06-07 21:31 ` Russ Cox
2009-06-05 0:07 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2009-06-03 14:56 hugo rivera
2009-06-03 16:21 ` Rodolfo (kix)
2009-06-03 17:34 ` erik quanstrom
2009-06-03 17:46 ` Rob Pike
2009-06-03 18:05 ` hugo rivera
2009-06-03 16:50 ` yy
2009-06-03 16:51 ` Russ Cox
2009-06-03 17:19 ` Enrique Soriano
2009-06-03 20:01 ` Wu JIANG
2009-06-03 20:05 ` Wu JIANG
2009-06-03 20:11 ` hugo rivera
2009-06-03 20:44 ` Wu JIANG
2009-06-03 20:49 ` hugo rivera
2009-06-03 23:32 ` J.R. Mauro
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=5484a4d7541fb835580f09a1448bc9d9@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).