site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Nov 16, 2009, at 7:21 AM, Clark Cox wrote:
On Mon, Nov 16, 2009 at 2:51 AM, Filip van der Meeren <filip@code2develop.com> wrote:
Hi,
Sorry if I am posting this on the wrong forum. But I really do not know where to post this message. Is it possible to archive/store a block?
I do not believe so. Think about what that would entail; it would have to save all of its code, as well as all of its context; and would have to do so in a way that would remain valid across process launches (what happens if someone archives a block in 32-bit code, but attempts to call it from 64-bit code, etc.)
I imagine that this is where using llvm to generate intermediary byte-code would be helpful. But preserving context would be the tricky part. If a block captures a pointer, that address won't be valid when you unarchive the block. You'd have to store what that address points to, load it into memory at unarchiving time and then update the block's captured pointer accordingly. So it gets really unwieldy when you start introducing things like CoreFoundation objects or Objective-C objects that don't comply with NSCoder. And it gets even worse if you're calling any API from within your block and assuming a certain state in the framework backing that API. The block has no idea what the framework's backing state is (maybe the framework needs to initialize a global, or certain things your program has done beforehand have changed that state from its initial value), so it can't capture that context and reinitialize. -- Damien Sorresso BSD Engineering Apple Inc. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com