Re: Two interoperable implementations rule
Maciej Stachowiak wrote: The WebKit project will accept patches for any feature of 3.1 that has been reconciled with 4, and we will likely devote Apple resources to implementing such features as well, so SquirrelFish will likely be a candidate for one of the interoperable implementations. Mozilla also has an extensive test suite for ECMAScript 3rd edition, which could be a good starting point for an ES3.1 test suite. Not being familiar with the webkit code base or process for accepting patches, can you point me to where I can find out more? - Sam Ruby ___ Es4-discuss mailing list Es4-discuss@mozilla.org https://mail.mozilla.org/listinfo/es4-discuss
Re: Two interoperable implementations rule
On Jul 14, 2008, at 8:12 AM, Sam Ruby wrote: Maciej Stachowiak wrote: The WebKit project will accept patches for any feature of 3.1 that has been reconciled with 4, and we will likely devote Apple resources to implementing such features as well, so SquirrelFish will likely be a candidate for one of the interoperable implementations. Mozilla also has an extensive test suite for ECMAScript 3rd edition, which could be a good starting point for an ES3.1 test suite. Not being familiar with the webkit code base or process for accepting patches, can you point me to where I can find out more? Sure! Here's basic instructions on how to check out, build and debug the code (applicable to Windows and Mac, the Gtk and Qt ports have their build processes documented elsewhere): http://webkit.org/building/checkout.html http://webkit.org/building/build.html http://webkit.org/building/run.html Here's an overview of the process for contributing: http://webkit.org/coding/contributing.html And here is contact info: http://webkit.org/contact.html These links and a lot more info are all on the front page of http://webkit.org/ Regards, Maciej ___ Es4-discuss mailing list Es4-discuss@mozilla.org https://mail.mozilla.org/listinfo/es4-discuss
Re: Newly revised Section 10 for ES3.1.
On Mon, Jul 14, 2008 at 11:08 AM, Sam Ruby [EMAIL PROTECTED] wrote: Mike Shaver wrote: I can't see why not -- we'll certainly be looking to implement forthcoming editions of ECMAScript, and if decimal is a part of it then your code would certainly be helpful! Did you say if? Grrr Yes? I didn't think that ES3.1 or ES4 had committed to decimal, and in what form. Things are still being cut from both, last I checked; I meant no offense. In any case, how about Firefox 3.1 then? :-) Not really the forum for product-delivery discussions, but I think it would be reasonable to propose. Worth filing and nominating, certainly. I have 81,000+ tests ready to be ported over for decNumber, and can produce tests for the instance methods. Excellent! Mike ___ Es4-discuss mailing list Es4-discuss@mozilla.org https://mail.mozilla.org/listinfo/es4-discuss
Re: Two interoperable implementations rule
On Fri, Jul 11, 2008 at 7:10 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote: This may be tricky to define, since many possible candidate implementations are open source and developed collaboratively by community contributors and overlapping sets of vendors. For example, would Rhino and SpiderMonkey count as sufficiently independent implementations? Similarly, if we end up with, f.e., both WebKit and Spidermonkey using decNumber as our internal implementation of Decimal, does that count as two interoperable implementations? It seems like we'd be at risk of mostly testing that code against itself, so I would hope that we look for such reuse cases when we're making sure that we actually have usefully-distinct implementations of features to validate the spec. chuckle Isn't that the idea of open-source software -- that by using the same software you get the same results (fdlibm, for example)? But a good point .. the 'new' issue here is that the same code in the different environments ends up with the same calls to the underlying library and yields the same results. (The decNumber code is quite stable, for example -- averaging fewer than one detected bug/year since its first release in 2001, is used in numerous IBM, SAP, and other vendors' products, and is part of the verification suite for power.org, PowerPC, and IBM mainframe hardware.) Mike Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ___ Es4-discuss mailing list Es4-discuss@mozilla.org https://mail.mozilla.org/listinfo/es4-discuss
Re: Two interoperable implementations rule
On Mon, Jul 14, 2008 at 4:37 PM, Mike Cowlishaw [EMAIL PROTECTED] wrote: (The decNumber code is quite stable, for example -- averaging fewer than one detected bug/year since its first release in 2001, is used in numerous IBM, SAP, and other vendors' products, and is part of the verification suite for power.org, PowerPC, and IBM mainframe hardware.) I have no doubt; it's more whether the spec is sufficiently detailed and clear that someone can work from it and produce an interoperable implementation without using the same software impl. Otherwise the spec can just include the decNumber source in an appendix, I guess. :) Mike ___ Es4-discuss mailing list Es4-discuss@mozilla.org https://mail.mozilla.org/listinfo/es4-discuss
Re: Proposed ES4 draft 2
These documents are now available on the wiki in HTML as well as PDF formats: http://wiki.ecmascript.org/doku.php?id=spec:spec Jd On 7/11/08 4:59 PM, Jeff Dyer wrote: Enclosed is an update to the draft ES4 specs. This includes revisions of the introduction, grammar and core-language specs of draft 1 (16-May) as well as an initial draft of the library spec. Also included are files that show the differences between draft 1 and draft 2 specs. There have been substantial changes to the text of the core-language spec and so the difference file for that spec is quite noisy. Two changes that contribute significantly to the noise are the renaming of rib to fixture map, and the simplification of the name resolution algorithms (in particular reducing the required number of search passes from two to one). These specs should be the basis for technical discussions of ES4 on es4-discuss and at the July 23 Oslo meeting. Enjoy! Jd [Patrick, please assign appropriate document numbers and post to the internal TC39 repository. Thanks!] ___ Es4-discuss mailing list Es4-discuss@mozilla.org https://mail.mozilla.org/listinfo/es4-discuss
