> > > 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. 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? - erik
