From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <98e535534bd51792a5db3b7af4034fc6@quanstro.net> References: <3e1162e60909030844r8760a8fu1b27d6e60965ecfb@mail.gmail.com> <98e535534bd51792a5db3b7af4034fc6@quanstro.net> Date: Thu, 3 Sep 2009 11:56:05 -0700 Message-ID: <3e1162e60909031156l54ad6e1jbce390dfbe697718@mail.gmail.com> From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd29a208c8f120472b0ef9a Subject: Re: [9fans] "Blocks" in C Topicbox-Message-UUID: 61e826ac-ead5-11e9-9d60-3106f5b1d025 --000e0cd29a208c8f120472b0ef9a Content-Type: text/plain; charset=ISO-8859-1 On Thu, Sep 3, 2009 at 9:02 AM, erik quanstrom wrote: > > 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. > > Apple's using it all over the place in Snow Leopard, in all their native apps to write cleaner, less manual-lock code. At least, that's the claim :-). If by node you mean "single machine" then I suppose I agree, but this is not a distributed computing solution in the world of multi-node programming. Dave > - erik > > --000e0cd29a208c8f120472b0ef9a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Sep 3, 2009 at 9:02 AM, erik qua= nstrom <quans= tro@quanstro.net> wrote:
> The blocks aren't interesting at all by themselv= es, I totally agree with
> that. =A0However 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 wh= ere
> the real power comes out.

this reminds me of paul and byron's shell, es which had
anonymous blocks. =A0in 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.


Apple&#= 39;s using it all over the place in Snow Leopard, in all their native apps = to write cleaner, less manual-lock code. =A0At least, that's the claim = :-).

If by node you mean "single machine" then I s= uppose I agree, but this is not a distributed computing solution in the wor= ld of multi-node programming.

Dave
=A0
- erik


--000e0cd29a208c8f120472b0ef9a--