From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain Date: Fri, 4 Sep 2009 14:54:25 -0700 From: Roman V Shaposhnik In-reply-to: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-id: <1252101265.16936.6659.camel@work.SFBay.Sun.COM> References: Subject: Re: [9fans] "Blocks" in C Topicbox-Message-UUID: 6549eb64-ead5-11e9-9d60-3106f5b1d025 On Fri, 2009-09-04 at 13:42 -0400, erik quanstrom wrote: > as i believe was originally explained, > i ripped that example *directly* from the apple grand central > documentation on page 37 in the "Data Types" section: > > http://developer.apple.com/mac/library/documentation/Performance/Reference/GCD_libdispatch_Ref/GCD_libdispatch_Ref.pdf > > maybe you don't believe the documentation? Sure I do. I also believed in Apple doing the right thing here :-( Anyway, the only thing I can say in my defense here is that since your example was mixed among pretty funny speculations about executable code being copied to the stack and such I couldn't possible imagine that it came from the docs *verbatim*. Thanks, Roman. P.S. And yes, technically -- it is up to compiler to either have or not have that limitation, since the blocks that you create within a function scope are all *known* to it and can be rearranged at will.