From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dataflow programming from shell interpreter
Date: Mon, 18 Jan 2010 06:15:37 -0500 [thread overview]
Message-ID: <5050b89d9c59adfd0f78ae8d2809f5bd@ladd.quanstro.net> (raw)
In-Reply-To: <c563b2f7-92ac-463a-864c-267721ddb30a@k35g2000yqb.googlegroups.co>
On Mon Jan 18 06:08:05 EST 2010, climber.tim@gmail.com wrote:
> Is this possible for UNIX philosophy to develop further? Let's say,
> XML-coded trees or graphs instead of one-line strings in stdin/
> stdout.Or LISP S-expressions. New set of utilities for filtering such
> streams, grep for XML trees, etc. Building environment for dataflow
> programming from shell interpreter.
> Any interesting papers exist on this topic?
not on xml per se. but rob did some work with structured
regular expressions that sound a lot like what you describe,
except there is no xml.
Rob Pike, Structural regular expressions.
Proceedings of the European UNIX User's Group Conference. EUUG, Helsinki, Finland.
doc.cat-v.org/bell_labs/structural_regexps/se.pdf
- erik
next parent reply other threads:[~2010-01-18 11:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c563b2f7-92ac-463a-864c-267721ddb30a@k35g2000yqb.googlegroups.co>
2010-01-18 11:15 ` erik quanstrom [this message]
[not found] <58d8d6b4960925aab27312e0968a3e26@quintile.net>
2010-01-18 19:39 ` Eric Van Hensbergen
2010-01-18 10:58 Tim Climber
2010-01-18 12:19 ` Steve Simon
2010-01-18 20:04 ` Tim Newsham
2010-01-19 9:59 ` Aharon Robbins
2010-01-19 15:40 ` Steve Simon
2010-01-20 21:13 ` Eris Discordia
2010-01-20 21:41 ` Patrick Kelly
2010-01-21 8:00 ` roger peppe
2010-01-21 12:45 ` maht
2010-01-21 21:36 ` Skip Tavakkolian
2010-01-22 9:44 ` Eris Discordia
2010-01-19 22:13 ` Andy Spencer
2010-01-18 16:23 ` Eric Van Hensbergen
2010-01-18 19:23 ` Aharon Robbins
2010-01-19 22:33 ` Andy Spencer
2010-01-27 10:44 ` Sam Watkins
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=5050b89d9c59adfd0f78ae8d2809f5bd@ladd.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).