From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <98e535534bd51792a5db3b7af4034fc6@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu,  3 Sep 2009 12:02:56 -0400
To: 9fans@9fans.net
In-Reply-To: <3e1162e60909030844r8760a8fu1b27d6e60965ecfb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] "Blocks" in C
Topicbox-Message-UUID: 6199d52e-ead5-11e9-9d60-3106f5b1d025

> The blocks aren't interesting at all by themselves, I totally agree with
> that.  However what they do to let you write a function inline, that can be
> pushed to another function, to be executed on a concurrent FIFO, is where
> the real power comes out.

this reminds me of paul and byron's shell, es which had
anonymous blocks.  in fact, that's how the if statement
worked.

in c, i don't see why such a bolt-on would be useful in
c, especially since your concurrent fifo would be limited
to one shared-memory node unless you're going to add a runtime
compiler.

- erik