On Tue, Apr 13, 2010 at 5:41 PM, Reko Tiira <[email protected]> wrote:
> The whole point of the example was that > while a thread is sleeping (and unlocked), some other thread might > create a HandleScope that will then "own" the variables created after > the thread wakes up, without the programmer really knowing about it. > The problem is with the fact that HandleScope's aren't really owned by > any thread, so when the control returns to the first thread, it'll > happily use the latest created HandleScope; even if it was created in > the other thread. > Ah, i see. i unfortunately have no answer but would love to hear one. > But I think I'll just do what you suggested, and don't use > HandleScopes at all. Thanks for the feedback! > If i'm not mistaken, handlescopes are implicitly created as part of callback function bindings, so removing them might not solve the problem. (???) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users To unsubscribe, reply using "remove me" as the subject.
