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).
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.