Hi, I'm using a C++ lambda to represent the callback state for a Javascript
callback and wanted to solicit some feedback on this approach. I thought
this would be an elegant way to set up the C++ binding. Here is some
example code from the Javascript side:
var i = new Thing();
i.callback = fu
On Wed, Feb 11, 2015 at 8:38 PM, Wenyuan Yu wrote:
> Thanks! Any reason why sharing even immutable objects is not supported in
> v8?
>
Only one thread at a time can run in a given isolate, so if you want
multiple threads to run at the same time, they each need a different
isolate. As the name im
Thanks! Any reason why sharing even immutable objects is not supported in
v8? Are you aware of any js engine in wild with this ability?
I am not writing the server code from scratch, but wanting to extend a C++
service with ability to change some flexible logic without pushing compiled
code...
I'm trying to get one of the boards, but it make take a few days. In the
meantime, can you try to run 'd8' shell directly. In a normal build this would
be in out/mips.release/d8. Please let me know if that comes up OK, or if not,
what messages are printed. If it is broken, you could also try bui
That is correct, the base requirement for v8 is ARMv6 with VFPv2.
Rodolph.
On 11 February 2015 at 14:46, Michael Boldischar <
michael.j.boldisc...@gmail.com> wrote:
> Is ARMv5 still supported by the V8 engine? I had trouble with NodeJS and
> someone suggested that ARMv5 support was dropped by t
Is ARMv5 still supported by the V8 engine? I had trouble with NodeJS and
someone suggested that ARMv5 support was dropped by the V8 engine:
https://groups.google.com/forum/#!topic/nodejs/kNBQq6-srAw
Thanks!
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/
Nope, sharing things across threads is not possible.
Also, there is a certain cost associated with each unique thread that uses
a given V8 instance. So for scenarios like yours, it's advisable to have a
pool of long-running worker threads (instead of spawning and discarding a
new thread for every
Since I'm cross-compiling rather than building natively on a target I think
that :
*snapshot=off*
is the right choice also according to what I have read over the internet. I
have re-built both the v8 package and node.js. V8 is built now with the
default options for mips architecture as we d
On Wed, Feb 11, 2015 at 12:54 AM, Malek Musleh
wrote:
> Could you pinpoint the location (highest level routine) where the IC
> is accessed, and thus determined if its a hit/miss.
There is no such location. That's kind of the point of having ICs. C++ code
is only called when the generated handle
