From: "J. R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: "9fans@9fans.net" <9fans@9fans.net>
Subject: Re: [9fans] Recursive structural expressions?
Date: Fri, 21 Aug 2009 09:58:59 -0400 [thread overview]
Message-ID: <355A8710-222E-45FA-9B28-6FB58565A7C2@gmail.com> (raw)
In-Reply-To: <a85dde21bb450f779bc73f5c904cfa55@quanstro.net>
On Aug 20, 2009, at 21:01, erik quanstrom <quanstro@quanstro.net> wrote:
>> Here's an example. Let's make the syntax extra pukey: @#, where # is
>> 1-9, defines a `named procedure', which is the same thing as putting
>> something in braces in Sam.
>>
>> x/.*\n/ @1{ ( @1 ) | @1 ( @1 ) ( ) | }
>>
>
> x/re/ repeatedly sets . with matches until the input
> is exhausted. so i don't think i understand your example.
> how does /.*\n/{(.*\n)|.*\n(.*\n)|} match anything
> but the tautological .*\n|? for example, if the input
> is "line1\nline2\n", then . is in turn "line1\n" and "line2\n",
> and both match .*\n|.
>
> where do the actions go in your example?
I guess I botched the example a bit. The whole part after the @ should
be in an x//, and the actions would come after. Something more
complicated would allow you to match any parenthetical expression on a
line and alter it, which could be useful.
>
> - erik
>
next prev parent reply other threads:[~2009-08-21 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 17:52 J.R. Mauro
2009-08-20 19:53 ` erik quanstrom
2009-08-20 20:33 ` J.R. Mauro
2009-08-20 20:39 ` erik quanstrom
2009-08-20 21:14 ` J.R. Mauro
2009-08-20 21:26 ` erik quanstrom
2009-08-21 0:21 ` J.R. Mauro
2009-08-21 1:01 ` erik quanstrom
2009-08-21 1:14 ` Charles Forsyth
2009-08-22 1:10 ` J.R. Mauro
2009-08-23 19:59 ` Aharon Robbins
2009-08-23 21:27 ` Rob Pike
2009-08-21 13:58 ` J. R. Mauro [this message]
2009-08-21 14:24 ` Russ Cox
2009-08-21 14:57 ` 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=355A8710-222E-45FA-9B28-6FB58565A7C2@gmail.com \
--to=jrm8005@gmail.com \
--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).