Re: [v8-users] Make v8 project more package managers friendly

2013-10-04 Thread Louis Santillan
Jochen, Could you elaborate on "copy the icu.gyp file somewhere else and point icu_gyp_path to it"? I hate pulling 100's of MB that I'm not using. Would 'svn co icu46/icu.gyp' suffice? I'm building with i18nsupport=off. -L On Thu, Oct 3, 2013 at 11:55 PM, Jochen Eisinger wrote: > > > > On Fr

Re: [blink-dev] Re: [v8-users] Intent to Implement Promises in V8

2013-10-04 Thread Vyacheslav Egorov
Recently I was made aware of a user land promises library that Petka Antonov (cced) implemented with the focus on performance. https://github.com/petkaantonov/bluebird There seem to be some meaningful benchmarks mentioned there in the section about Benchmarking. You might be interested in taking

Re: [v8-users] Make v8 project more package managers friendly

2013-10-04 Thread Paweł Hajdan , Jr .
Hey Anatol, please also take a look at https://groups.google.com/a/chromium.org/d/forum/chromium-packagers which is specifically for packagers and also includes V8/gyp packaging issues. Feel free to take a look at how Gentoo does things, e.g. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86

Re: [blink-dev] Re: [v8-users] Intent to Implement Promises in V8

2013-10-04 Thread Yusuke SUZUKI
> > We're currently working on adding a threading API, probably similar to > blink's WebThread. Sounds very nice. Providing embedder-side's threading operation interfaces to V8 is needed for Promises. Is there already any discussion about design of a threading API? On Sat, Oct 5, 2013 at 2:50 A

Re: [blink-dev] Re: [v8-users] Intent to Implement Promises in V8

2013-10-04 Thread Jochen Eisinger
To clarify, we won't expose threads to the language, but clean-up the thread usage of V8 internally, e.g. the optimizing compiler thread. best -jochen On Fri, Oct 4, 2013 at 7:37 PM, Dirk Pranke wrote: > On Fri, Oct 4, 2013 at 3:29 AM, Jochen Eisinger wrote: > >> >> We're currently working on

Re: [v8-users] How to execute code with a specific object as 'this'

2013-10-04 Thread CRLF0710
Thanks, i will implement it this way. 2013/10/4 Ben Noordhuis : > On Thu, Oct 3, 2013 at 5:11 PM, ChaRles Lew wrote: >> Hi, i'm a newbie on using v8. I'm trying to embedded v8 into a c++ >> application and provide javascript as an extension language. >> Now i'm seeking a way to invoke javascript

[v8-users] Re: [blink-dev] Intent to Implement Promises in V8

2013-10-04 Thread Dmitry Lomov
Implementing behind the flag LGTM. There is clear consensus among TC39 members, browser vendors and web platform champions that Promises are an important addition to ECMAScript. At a Sept TC39 meeting, promises has been put on a fast track to ES6 - the next release of ECMAScript spec. Also, Module

Re: [v8-users] Intent to implement and ship: ArrayBuffer.isView

2013-10-04 Thread Daniel Clifford
Compatibility risk and implementation complexity are low, support appears very high. I think this a good candidate for fast-tracking. Danno On Wed, Oct 2, 2013 at 11:29 AM, Dmitry Lomov wrote: > ArrayBuffer.isView(obj) is a static function that returns boolean > indicating whether the passed

Re: [v8-users] Intent to Implement Promises in V8

2013-10-04 Thread Jochen Eisinger
On Fri, Oct 4, 2013 at 12:19 PM, Yutaka Hirano wrote: > Promises are currently being specified at [1] and according to [2] they > will be introduced in ES6. > I would like to implement them behind a flag. > The implementation will replace the Promises implementation in Blink in > the future. > >

[v8-users] Intent to Implement Promises in V8

2013-10-04 Thread Yutaka Hirano
Promises are currently being specified at [1] and according to [2] they will be introduced in ES6. I would like to implement them behind a flag. The implementation will replace the Promises implementation in Blink in the future. Other implementations Promises are also defined in whatwg[3] and so

Re: [v8-users] Make v8 project more package managers friendly

2013-10-04 Thread Jakob Kummerow
In addition to what has been said already: 1) The V8 build does not automatically pull in either ICU or GYP. You have to explicitly run "make dependencies" to download them, which is merely a convenience feature. So there's no need to "turn that off" -- simply run "make native" or "make ia32.relea