Re: [v8-users] Is V8::JSON::Parse really needed against JSON inputs?

Of course it's possible to make C++ objects accessible to JS, that's what V8's API is for. You'll have to provide accessors for fields you want to expose. See https://github.com/v8/v8/wiki/Embedder's-Guide#accessing-dynamic-variables. On Thu, Mar 16, 2017 at 6:04 PM, Abhishek Singh

Re: [v8-users] Is V8::JSON::Parse really needed against JSON inputs?

Hi, (responses inline) > On 16-Mar-2017, at 21:53, Jakob Kummerow wrote: > > What do you mean by "native JS JSON"? > Apologies, it isn’t technically correct term. I meant javascript object carved out of string representation. > JSON ("JavaScript Object Notation") is

[v8-users] Is V8::JSON::Parse really needed against JSON inputs?

Hi, I'm trying to send JSON data to user supplied JS code, which is executed by V8. What I've realised is even if user data is JSON marshalled, I've to explicitly do V8::JSON::Parse on it, so that value received in JS world is native JS JSON. Is that really necessary? Performance penalty

Re: [v8-users] ASCII null character in script

V8 works towards implementing the ECMAScript spec, which you can find at https://tc39.github.io/ecma262/ . It doesn't provide any compatibility modes for other versions of JavaScript shipped by particular browsers, or historical versions of JavaScript. In standard JS, the null byte is not a

[v8-users] ASCII null character in script

Hello there, I have been given a script sample that contains a null character (ASCII 0x00). alert("I am an alert box!"); ^@ Obviously, this fails to compile and run, since this is not valid syntax (I get "SyntaxError: Invalid or unexpected token"). However, in IE this code