Re: [v8-users] C++ lifetime management via shared_ptr and

2013-05-24 Thread Stephan Beal
On Fri, May 24, 2013 at 9:58 PM, Jim Acquavella wrote: > Thanks Stephan! I'm surprised and disappointed I can't guarentee my C++ > objects will be destroyed. Can anyone from Google comment on this? There > must be a way to force everything allocated to be released at shutdown, no?! > That hors

[v8-users] Harmony Modules and Loaders

2013-05-24 Thread Joe Wood
As the implementation currently stands, does the harmony support in v8 extend to loading modules in a different file statically? Does V8 depend on a application supplied module loader? I'm trying this: in external.js module external { var x = 10; export function gotit() { return x++;

Re: [v8-users] C++ lifetime management via shared_ptr and

2013-05-24 Thread Jim Acquavella
Thanks Stephan! I'm surprised and disappointed I can't guarentee my C++ objects will be destroyed. Can anyone from Google comment on this? There must be a way to force everything allocated to be released at shutdown, no?! On Fri, May 24, 2013 at 8:35 AM, Stephan Beal wrote: > On Fri, May 24,

Re: [v8-users] cctests

2013-05-24 Thread Jakob Kummerow
Sure, given how make works, you can build any individual output file. The default "all" meta target is just convenience. On Thu, May 23, 2013 at 11:47 PM, mschwartz wrote: > Is there a way to build v8 without building the cctest/ tree? > > When I do > make x64.release > > I see it build all

Re: [v8-users] C++ lifetime management via shared_ptr and

2013-05-24 Thread Stephan Beal
On Fri, May 24, 2013 at 1:53 AM, wrote: > virtual ~Point() > { > assert(false); // Never called! > } > v8 does not guaranty that it will _ever_ call your destructors. It does _not_ clean up automatically when it shuts down. This of course makes life difficult for types which require proper closi

Re: [v8-users] Execution efficiency of forEach function in google V8 engine

2013-05-24 Thread Jakob Kummerow
On Fri, May 24, 2013 at 3:53 AM, 刘玉龙 wrote: > Hey, I have another question. > > I noticed that jquery, underscore and some other libraries, don't check if > the index is in array. Under what circumstances this lacking of check will > cause a bug? > That depends on your definition of "bug"; or, p