The more verbose locker documentation can be found here: http://bespin.cz/~ondras/html/classv8_1_1Unlocker.html
I was reading docs straight out of v8.h, call me old fashioned :) On Fri, Jun 24, 2011 at 6:58 AM, Stephan Beal <[email protected]> wrote: > On Thu, Jun 23, 2011 at 9:42 PM, Marcel Laverdet <[email protected]>wrote: > >> 7 lines? The Locker documentation I'm seeing is 76 lines long. It's >> actually above the Unlocker class in v8.h. >> > > i'm looking at the API docs (via doxygen). i'm not aware of any other docs > other than the "Embedder's Guide", which i (hopefully) outgrew a couple > years ago. > > Perhaps it seems a bit more clear to me since I've already written an >> application which needs to use Locker and Unlocker extensively. I think in >> the comment "Methods below this point require holding a lock (using Locker) >> in a multi-threaded environment" you need to note well the qualifier "in a >> multi-threaded environment". In a single-threaded environment there's no >> locking that needs to take place. >> > > You're right - the MT qualifier discounts my complaint. > > I don't think the default lock is explicit under the hood. The Locker code >> is actually very isolated from the rest of v8, most code just assumes that >> there is a lock and Locker calls a ton of hooks on lock \ unlock. So yeah >> it's more like "there's only one thread, so it's locked". >> > > Fair enough. The whole topic of isolates is still voodoo to me, though. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
