[v8-users] calling C++ from javascript: how to modify an input argument?

For example, I can get a uint like this in a C++ function: uint32_t myuint32 = args[0]->Int32Value(); But is it also possible to change the value somehow from C++ land, so that in javascript the variable passed into the function will reflect the changed value? If this is possible with some C++

Re: [v8-users] Creating and locking Isolates

Thanks Dmitry, but the problem happens even when I'm not calling Enter before acquiring the lock. Any other ideas? Thanks. On Tuesday, April 22, 2014 6:15:50 PM UTC+3, Dmitry Lomov wrote: > > You should always enter isolates _after_ you acquired a lock on it, not > before. > You do not need t

Re: [v8-users] V8 on Windows Server 2012

Thanks for the reply Ben, The V8 dll is placed the same directory as the executing program, but it's almost like the runtime just does not recognize it. Same folder placed in windows 7 works perfectly. On Tuesday, April 22, 2014 12:06:21 PM UTC-4, Ben Noordhuis wrote: > > On Tue, Apr 22, 20

Re: [v8-users] V8 on Windows Server 2012

On Tue, Apr 22, 2014 at 5:47 PM, Jason wrote: > Hi, > > has anyone tried using v8 on windows server 2012? I have a .net C++ class > that wraps the v8.dll, the code works properly on windows 7 64 bits, but on > windows 2012, it would say "unable to load one of it's dependencies. The > specified m

Re: [v8-users] V8::Dispose() Segmentation fault

On Mon, Apr 21, 2014 at 11:15 PM, David Wardell wrote: > You are a genius. > > I simply placed all the objects (excluding the Isolate) in a sub-block and > then called dispose after this sub-block (thus forcing the other objects' > destructors before the call to Dispose()). > > It even got rid of

[v8-users] V8 on Windows Server 2012

Hi, has anyone tried using v8 on windows server 2012? I have a .net C++ class that wraps the v8.dll, the code works properly on windows 7 64 bits, but on windows 2012, it would say "unable to load one of it's dependencies. The specified module could not be found", The v8.dll was built for x6

Re: [v8-users] Creating and locking Isolates

You should always enter isolates _after_ you acquired a lock on it, not before. You do not need to use Enter directly: Isolate::Scope is RIAA-style wrapper around Isolate::Enter/Exit. HTH, Dmitry On Tue, Apr 22, 2014 at 4:50 PM, Nozik wrote: > Hi all, > > I've upgraded an old V8 to an updated

[v8-users] Creating and locking Isolates

Hi all, I've upgraded an old V8 to an updated version and encountered the following problem: I'm creating Isolates several times in the code, and then calling the Locker. _isolate = Isolate::New(); > _isolate->Enter(); > Locker lock(_isolate); > Isolate::Scope isolateScope(_isolate); Howeve