9 Mar 2010 05:50
9 Mar 2010 06:01
Re: v8 and ecmascript 5 strict
good info on the benefits of strict mode here: http://ejohn.org/blog/ecmascript-5-strict-mode-json-and-more/ On Mar 9, 4:50 am, billywhizz <apjohn...@...> wrote: > does anyone know if v8 will eventually support the ecmascript 5 strict > mode and the full set of 5th edition features? i've been googling but > can't find the answer. -- -- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@... To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 06:08
Re: v8 and ecmascript 5 strict
On Mon, Mar 8, 2010 at 11:50 PM, billywhizz <apjohnsto@...> wrote: > does anyone know if v8 will eventually support the ecmascript 5 strict > mode and the full set of 5th edition features? Since v8 tracks javascriptcore, that's the place to look, specifically at this [1] overview of ES5 features in JSC. [1] http://labs.trolltech.com/blogs/2010/01/15/ecmascript-5-and-webkitjavascriptcore/ Looks like there's a bug for pretty much everything except "use strict".
9 Mar 2010 11:07
Re: v8 and ecmascript 5 strict
On 09/03/2010, at 06:08, Karl Guertin wrote: > On Mon, Mar 8, 2010 at 11:50 PM, billywhizz <apjohnsto@...> wrote: >> does anyone know if v8 will eventually support the ecmascript 5 strict >> mode and the full set of 5th edition features? > > Since v8 tracks javascriptcore, that's the place to look, specifically > at this [1] overview of ES5 features in JSC. I think v8 and jsc are completely separate projects. http://code.google.com/p/v8/ http://webkit.org/projects/javascript/index.html -- -- Jorge.
9 Mar 2010 11:40
Re: v8 and ecmascript 5 strict
On Tue, Mar 9, 2010 at 11:07 AM, Jorge Chamorro <jorge-JoKmXD0gkCciovoLTrHv/AC/G2K4zDHf@public.gmane.org> wrote:
On 09/03/2010, at 06:08, Karl Guertin wrote:I think v8 and jsc are completely separate projects.
> On Mon, Mar 8, 2010 at 11:50 PM, billywhizz <apjohnsto-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> does anyone know if v8 will eventually support the ecmascript 5 strict
>> mode and the full set of 5th edition features?
>
> Since v8 tracks javascriptcore, that's the place to look, specifically
> at this [1] overview of ES5 features in JSC.
they are, but v8 tries to be as compatible to jsc as possible.
cheers,
sifu
http://code.google.com/p/v8/
http://webkit.org/projects/javascript/index.html
--
Jorge.
--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To unsubscribe from this group, send email to nodejs+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 11:49
Re: v8 and ecmascript 5 strict
2010/3/9 Siegmund Führinger <sifu@...>: >> I think v8 and jsc are completely separate projects. > > they are, but v8 tries to be as compatible to jsc as possible. Specifically, the v8 team's policy is that they don't want to create an additional test point on the browser matrix, so Chrome's v8+Webkit attempts to act like Safari's JSC+Webkit. At least that's the idea. The browser team is willing to experiment/get ahead of Safari with features like websockets but the v8 group is pretty diligent about it. This annoys me because I'd like to use __noSuchMethod__ in a variety of APIs from node without waiting for an ES Harmony proxies implementation to land. -- -- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@... To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 12:03
Re: v8 and ecmascript 5 strict
On 09/03/2010, at 11:49, Karl Guertin wrote: > 2010/3/9 Siegmund Führinger <sifu@...>: >>> I think v8 and jsc are completely separate projects. >> >> they are, but v8 tries to be as compatible to jsc as possible. > > Specifically, the v8 team's policy is that they don't want to create > an additional test point on the browser matrix, so Chrome's v8+Webkit > attempts to act like Safari's JSC+Webkit. At least that's the idea. > The browser team is willing to experiment/get ahead of Safari with > features like websockets but the v8 group is pretty diligent about it. > > This annoys me because I'd like to use __noSuchMethod__ in a variety > of APIs from node without waiting for an ES Harmony proxies > implementation to land. I think that the DOM part of these two browsers' API evolves necessarily in parallel because it belongs 100% to the -common, shared- webkit part of them. I don't see how does that have anything to do with the DOM-less JS engines, v8 and jsc... ¿? -- Jorge. -- -- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@... To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 12:44
Re: v8 and ecmascript 5 strict
On Tue, Mar 9, 2010 at 6:03 AM, Jorge <jorge@...> wrote: > I think that the DOM part of these two browsers' API evolves necessarily in parallel because it belongs 100% to the -common, shared- webkit part of them. I don't see how does that have anything to do with the DOM-less JS engines, v8 and jsc... ¿? The idea is that if v8 and JSC have the same API then developers can save time by not having to test in both Safari and Chrome since they share the webkit rendering engine. If the v8 API doesn't match the JSC API then it's possible that you could write something in one that doesn't work in the other so you'd have to test everything in both. The bottom line is that while v8 is a completely separate project from JSC, the v8 developers are committed to implementing the same set of features that the JSC guys implement. If you want to know what's coming up in v8, you have to look at what's going into JSC. -- -- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@... To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 13:19
Re: v8 and ecmascript 5 strict
On 09/03/2010, at 12:44, Karl Guertin wrote: > On Tue, Mar 9, 2010 at 6:03 AM, Jorge <jorge@...> wrote: >> I think that the DOM part of these two browsers' API evolves necessarily in parallel because it belongs 100% to the -common, shared- webkit part of them. I don't see how does that have anything to do with the DOM-less JS engines, v8 and jsc... ¿? > > The idea is that if v8 and JSC have the same API then developers can > save time by not having to test in both Safari and Chrome since they > share the webkit rendering engine. If the v8 API doesn't match the JSC > API then it's possible that you could write something in one that > doesn't work in the other so you'd have to test everything in both. > > The bottom line is that while v8 is a completely separate project from > JSC, the v8 developers are committed to implementing the same set of > features that the JSC guys implement. If you want to know what's > coming up in v8, you have to look at what's going into JSC. I think that you're mixing the html DOM API (that webkit provides) with the JS engine (which provide an environment compatible with the EcmaScript specs, but no DOM). -- Jorge. -- -- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@... To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 13:43
Re: v8 and ecmascript 5 strict
On Tue, Mar 9, 2010 at 11:49 AM, Karl Guertin <grayrest <at> gmail.com> wrote:
2010/3/9 Siegmund Führinger <sifu <at> 0xx0.net>:>> I think v8 and jsc are completely separate projects.Specifically, the v8 team's policy is that they don't want to create
>
> they are, but v8 tries to be as compatible to jsc as possible.
an additional test point on the browser matrix, so Chrome's v8+Webkit
attempts to act like Safari's JSC+Webkit. At least that's the idea.
The browser team is willing to experiment/get ahead of Safari with
features like websockets but the v8 group is pretty diligent about it.
This annoys me because I'd like to use __noSuchMethod__ in a variety
of APIs from node without waiting for an ES Harmony proxies
implementation to land.
__noSuchMethod__ would make my life quite a bit easier. on the other hand i'm happy that the v8 API doesn't diverge from the JSC since this are the two engines i have to support in most of my projects.
JSC should just implement __noSuchMethod__.
cheers,
sifu
--You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To unsubscribe from this group, send email to nodejs+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 15:25
Re: v8 and ecmascript 5 strict
On 09/03/2010, at 13:43, Siegmund Führinger wrote: > > JSC should just implement __noSuchMethod__. <quote> __noSuchMethod__ is an effectively dead extension in spidermonkey, it is not being proposed for standardisation. To quote Brendan:" http://wiki.ecmascript.org/doku.php?id=harmony:proxies is the future" </quote> https://bugs.webkit.org/show_bug.cgi?id=18058 -- Jorge. -- -- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@... To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
9 Mar 2010 07:14
Re: v8 and ecmascript 5 strict
Thanks. On Mar 9, 5:08 am, Karl Guertin <grayr...@...> wrote: > On Mon, Mar 8, 2010 at 11:50 PM, billywhizz <apjohn...@...> wrote: > > does anyone know if v8 will eventually support the ecmascript 5 strict > > mode and the full set of 5th edition features? > > Since v8 tracks javascriptcore, that's the place to look, specifically > at this [1] overview of ES5 features in JSC. > > [1]http://labs.trolltech.com/blogs/2010/01/15/ecmascript-5-and-webkitjav... > > Looks like there's a bug for pretty much everything except "use strict". -- -- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@... To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
RSS Feed