Re: [v8-users] Exposing nested maps from C++ into JS world

I commented on the example On Thu, Jul 28, 2016 at 2:14 PM Abhishek Singh wrote: > Please find standalone code simulating your suggestion - > https://gist.github.com/abhi-bit/d3a2910ec54a47ce8294c2cc0c4bef93 (In the > comment pasted output in my case). Will appreciate if you could guide using >

Re: [v8-users] v8 gyp build fail

I wonder whether you have curl installed? On Thu, Jul 28, 2016 at 6:53 PM chaony wrote: > Hi, > I want to try v8 engine in my project, but it seems something wrong. I > do it in following way: > > 1. git clone: git clone > https://chromium.googlesource.com/chromium/tools/depot_tools.git > 2.

Re: [v8-users] Intent to Ship: Object.getOwnPropertyDescriptors()

On Thursday, July 28, 2016 at 3:23:41 PM UTC-4, Adam Klein wrote: > > +bcc blink-dev > > This lgtm to ship! A few questions/comments below. > > On Thu, Jul 28, 2016 at 12:03 PM, Caitlin Potter > wrote: > >> Object.getOwnPropertyDescriptors() has been implemented in V8 since >> February 2016, and

Re: [v8-users] Intent to Ship: Object.getOwnPropertyDescriptors()

+bcc blink-dev This lgtm to ship! A few questions/comments below. On Thu, Jul 28, 2016 at 12:03 PM, Caitlin Potter wrote: > Object.getOwnPropertyDescriptors() has been implemented in V8 since > February 2016, and enabled by the "Experimental Javascript Features" flag > in Chrome since March. Th

[v8-users] Intent to Ship: Object.getOwnPropertyDescriptors()

Object.getOwnPropertyDescriptors() has been implemented in V8 since February 2016, and enabled by the "Experimental Javascript Features" flag in Chrome since March. The feature has been ratified and is in the specification at https://tc39.github.io/ecma262/#sec-object.getownpropertydescriptors.

[v8-users] v8 gyp build fail

Hi, I want to try v8 engine in my project, but it seems something wrong. I do it in following way: 1. git clone: git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git 2. export path: export PATH=`pwd`/depot_tools:"$PATH” 3. fetch v8 with error: fetch v8 Running: gclien

Re: [v8-users] Re[3]: gyp_v8 error when building

Steve, I have to ask you to immediately stop this escalatory behavior. Failure to do so will result in a ban from this mailing list, and other chromium communication channels. best -jochen On Thu, Jul 28, 2016 at 2:50 PM Steve Paesani wrote: > I think you jumping in here with yout insults and

[v8-users] Re[3]: gyp_v8 error when building

I think you jumping in here with yout insults and further hostility proves my point. -- Sent from myMail app for Android Thursday, 28 July 2016, 06:46AM -04:00 from Ben Noordhuis i...@bnoordhuis.nl : >On Thu, Jul 28, 2016 at 12:00 PM, < spaesani.cons...@gmail.com > wrote: >> On a final note I

[v8-users] V8 Debugging protocol

Hi, I’m trying to hook in V8 JSON based debugger into a project. I was able to setup a breakpoint(line: 2 column: 0) against a OnUpdate function, sample function looks like this: ``` function OnUpdate(doc, meta) { log("doc meta id: ", meta.key); if (meta.type === "json" && doc.ssn) { log(

[v8-users] Re[3]: gyp_v8 error when building

1)Quite frankly I get by just fine without your code in my life. 2)You have no business jumping in on a conversation that was not in any way addressed to you on any capacity. -- Sent from myMail app for Android Thursday, 28 July 2016, 06:46AM -04:00 from Ben Noordhuis i...@bnoordhuis.nl : >On

Re: [v8-users] Exposing nested maps from C++ into JS world

Please find standalone code simulating your suggestion - https://gist.github.com/abhi-bit/d3a2910ec54a47ce8294c2cc0c4bef93 (In the comment pasted output in my case). Will appreciate if you could guide using this test script.

Re: [v8-users] Re: gyp_v8 error when building

On Thu, Jul 28, 2016 at 12:00 PM, wrote: > On a final note I just did a search and read what a "googler" is. > > Would have been nice to know v8 compilation isn't intended for non google > employees. > That's not true. Many non-Google-employees are compiling V8 regularly, and that's absolutely

Re: [v8-users] Re: gyp_v8 error when building

On Thu, Jul 28, 2016 at 12:00 PM, wrote: > On a final note I just did a search and read what a "googler" is. > > Would have been nice to know v8 compilation isn't intended for non google > employees. > > Rather hostile not to indicate it more clearly > > More hostile still not to have mentioned

Re: [v8-users] Exposing nested maps from C++ into JS world

I believe this is the change you wanted me to do: Local HTTPBody::WrapHTTPBodyMap() { EscapableHandleScope handle_scope(GetIsolate()); Local body_map_template = FunctionTemplate::New(GetIsolate()); body_map_template->InstanceTemplate()->SetHandler( NamedPropertyHandlerConfigurati

[v8-users] Re: gyp_v8 error when building

On a final note I just did a search and read what a "googler" is. Would have been nice to know v8 compilation isn't intended for non google employees. Rather hostile not to indicate it more clearly More hostile still not to have mentioned it here while I was struggling to build it. The more

Re: [v8-users] Re: gyp_v8 error when building

I think if you'd taken the time to read the post in it's entirety you'd see that I had considered the v8 build docs requiring setting a variable based on being a "googler" a joke thus prior to my own. You'd have also seen that I mentioned this to Michael, the person I was having a coversation w

Re: [v8-users] Exposing nested maps from C++ into JS world

I guess you should use function templates here. Local body_map_template = FunctionTemplate::New(isolate); body_map_template->InstanceTemplate()->SetHandler(...) body_map_template->InstanceTemplate()->SetInternalFieldCount(1); result = body_map_template->GetFunction()->NewInstance(); On Wed, Jul 2