ToString for Numbers: reducing variation.

2008-07-11 Thread David Jones
After I wrote a blog article on this subject someone suggested I raise the issue here. Currently, ECMA 262 3rd edition section 9.8.1, the ToString operator permits implementations to vary in how they convert certain numbers to strings. For example the number 5e-324 could legally be

Re: ToString for Numbers: reducing variation.

2008-07-11 Thread Waldemar Horwat
David Jones wrote: After I wrote a blog article on this subject someone suggested I raise the issue here. Currently, ECMA 262 3rd edition section 9.8.1, the ToString operator permits implementations to vary in how they convert certain numbers to strings. For example the number 5e-324

Two interoperable implementations rule

2008-07-11 Thread Maciej Stachowiak
On Jul 10, 2008, at 6:29 AM, [EMAIL PROTECTED] wrote: In a message dated 7/10/2008 3:03:12 A.M. Eastern Daylight Time, [EMAIL PROTECTED] writes: I do not believe that ECMA has the two interoperable implementations rule that the IETF and W3C have, but since ECMAScript is a standard of equal

Re: Two interoperable implementations rule

2008-07-11 Thread Anne van Kesteren
On Sat, 12 Jul 2008 00:01:26 +0200, Maciej Stachowiak [EMAIL PROTECTED] wrote: To be clear, I propose this rule not to block ES3.1, but to make it successful. The WebKit project will accept patches for any feature of 3.1 that has been reconciled with 4, and we will likely devote Apple

Re: Two interoperable implementations rule

2008-07-11 Thread Brendan Eich
On Jul 11, 2008, at 3:01 PM, Maciej Stachowiak wrote: On Jul 10, 2008, at 6:29 AM, [EMAIL PROTECTED] wrote: In a message dated 7/10/2008 3:03:12 A.M. Eastern Daylight Time, [EMAIL PROTECTED] writes: I do not believe that ECMA has the two interoperable implementations rule that the IETF

Re: Two interoperable implementations rule

2008-07-11 Thread Geoffrey Garen
Should a reference implementation, even if slow, count? My own opinion on this is no. Since, for the most part, a reference implementation doesn't face the performance and maintainability challenges that shipping software faces, I don't think it fleshes out the same issues that a real-world

Re: Two interoperable implementations rule

2008-07-11 Thread Anne van Kesteren
On Sat, 12 Jul 2008 00:54:05 +0200, Brendan Eich [EMAIL PROTECTED] wrote: The hurdle is certainly higher for ES4, although it may be less high given its reference implementation, which could pass the tests. Should a reference implementation, even if slow, count? FWIW, a reference

Re: Two interoperable implementations rule

2008-07-11 Thread Maciej Stachowiak
On Jul 11, 2008, at 3:49 PM, Jeff Dyer wrote: On 7/11/08 3:01 PM, Maciej Stachowiak wrote: 2) How is interoperability to be demonstrated? Do we accept good- faith claims of support, or do we need a test suite? I'd say that good faith is good enough. It's easy enough for us to check

Re: Two interoperable implementations rule

2008-07-11 Thread Brendan Eich
On Jul 11, 2008, at 4:06 PM, Geoffrey Garen wrote: Should a reference implementation, even if slow, count? My own opinion on this is no. Since, for the most part, a reference implementation doesn't face the performance and maintainability challenges that shipping software faces, I don't

RE: Two interoperable implementations rule

2008-07-11 Thread Allen Wirfs-Brock
A few thoughts on the general topic and various points that are been raised: Overall, I think this is a good idea. My personal opinion is that standardization should follow proven utility, not the other way around. However, it's difficult to get meaningful use of proposed web standards until

Re: Proposed ES4 draft 2

2008-07-11 Thread Eric Suen
Hi, Since FunctionExpression is PrimaryExpression, so the following statement: a = function() return b ? c : d; should be: a = fe ? c : d fe = function() return b or a = fe fe = function() return b ? c : d And same question for LetExpression. Regards, Eric Suen - Original Message