From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <580135a14ad078bb8223e7c448a5fa2b@quanstro.net> References: <3e1162e60909031213k5209f296vb0a77ff858e45496@mail.gmail.com> <580135a14ad078bb8223e7c448a5fa2b@quanstro.net> Date: Thu, 3 Sep 2009 12:50:43 -0700 Message-ID: <3e1162e60909031250v2914ab29s6e43e371f896712b@mail.gmail.com> From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd70e0cf2687e0472b1b2d7 Subject: Re: [9fans] "Blocks" in C Topicbox-Message-UUID: 6209b682-ead5-11e9-9d60-3106f5b1d025 --000e0cd70e0cf2687e0472b1b2d7 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Sep 3, 2009 at 12:36 PM, erik quanstrom wrote: > > > > 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 > > > > :-). > > > > > > could someone explain this to me? i'm just missing how > > > naming a block of code could change its locking properties. > > > > > > > > The explanation is in the manual I linked to earlier in this discussion. > If > > you want to see examples there's two I can think of available for > download. > > One is called DispatchLife the other is DispatchFractal. > > > > I've looked at DispatchLife, and there's no explicit locking of state for > > every cell being concurrently update in Conway's game of life. > > i can't find DispatchLife after a few minutes of googling. > i've read the manual, and it looks like csp to me. clearly > i am a reprobate outside the apple reality distortion field. > > Google doesn't have all the answers, I actually had to use Bing today, and it worked... anyway here's the link to DispatchLife. http://developer.apple.com/mac/library/samplecode/DispatchLife/ > could you explain why this isn't csp and why this can't be done > with regular c (that is why we need the concept of an > unnamed function pointer) and the thread library? > I'm actually planning to figure this stuff out a bit more and "blog" about it, hopefully by Friday sometime (tomorrow). I don't agree that any of this stuff is strictly needed. One can plod along with pthreads and do it wrong all day. One doesn't *need* C either, I've seen whole OSes for x86 written in assembly. It all depends on how much crap you want to keep track of. Dave > > - erik > > --000e0cd70e0cf2687e0472b1b2d7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Sep 3, 2009 at 12:36 PM, erik qu= anstrom <quan= stro@quanstro.net> wrote:
> > > Apple's using it all over the place in= Snow Leopard, in all their native
> > > apps to write cleaner, less manual-lock code. =A0At least, t= hat's the claim
> > > :-).
> >
> > could someone explain this to me? =A0i'm just missing how
> > naming a block of code could change its locking properties.
> >
> >
> The explanation is in the manual I linked to earlier in this discussio= n. =A0If
> you want to see examples there's two I can think of available for = download.
> =A0One is called DispatchLife the other is DispatchFractal.
>
> I've looked at DispatchLife, and there's no explicit locking o= f state for
> every cell being concurrently update in Conway's game of life.

i can't find DispatchLife after a few minutes of googling.
i've read the manual, and it looks like csp to me. =A0clearly
i am a reprobate outside the apple reality distortion field.


Google doesn't have all the answer= s, I actually had to use Bing today, and it worked... anyway here's the= link to DispatchLife.

http://developer.apple.com= /mac/library/samplecode/DispatchLife/
=A0
could you explain why this isn't csp and why this can't be done
with regular c (that is why we need the concept of an
unnamed function pointer) and the thread library?

=
I'm actually planning to figure this stuff out a bit more an= d "blog" about it, hopefully by Friday sometime (tomorrow). =A0

I don't agree that any of this stuff is strictly ne= eded. =A0One can plod along with pthreads and do it wrong all day. =A0One d= oesn't *need* C either, I've seen whole OSes for x86 written in ass= embly.

It all depends on how much crap you want to keep track = of.

Dave
=A0

- erik


--000e0cd70e0cf2687e0472b1b2d7--