Benjamin Byholm

Regarding C++ versions available: The worst compiler which can successfully compile any given version of Node (including V8) sets the bar. C++11 (g++ 4.8, VS 2013, clang whatever) for Node...

@ofrobots Any idea what could be up with this?

I thought something similar based on the stack trace, but then the documentation needs updating, since it cannot be used with `ObjectWrap`.

I'll start by noting that not using templates leads to very clumsy code, and since V8 makes heavy use of templates, this would require not directly exposing anything from V8....

Would definitely want a code generator to generate the code for all the ensuing virtually identical wrapper functions with different types. It would be nice if one could get at...

I agree that we have to start simple, implementation-wise. However, that initial implementation needs to scale up to offering a richer feature set. It does not need to be written...

Something like this should do. https://github.com/martine/v8c/blob/v8c/src/v8c.cc On May 14, 2015 10:46:57 PM EEST, Trevor Norris [email protected] wrote: > > It does not need to be written in C as such,...

And new V8. Notice that this project has been abandoned for 6 years. On May 14, 2015 11:00:11 PM EEST, Trevor Norris [email protected] wrote: > @kkoopa good stuff. we'd just...

So, what we'd essentially want is to wrap v8's C++ exports in C exports to get a stable ABI and then have a (NAN-derived) header library on top of that...

Clearly yes. The overhead of context switching from JavaScript to C++ drowns out everything else. On Friday 15 May 2015 03:06:11 Trevor Norris wrote: > @kzc After doing testing in...