On Nov 10, 2007, at 8:00 PM, Mark Miller wrote:
* To prevent these new keywords breaking ES3 compatibility, these
keywords are only recognized when a version attribute on the script
tag says the script is in ES4.
This has happened before, FYI -- from ES1-3 under various vendor
On Nov 10, 2007 9:10 PM, Brendan Eich [EMAIL PROTECTED] wrote:
On Nov 10, 2007, at 8:00 PM, Mark Miller wrote:
[out of order]
* The intersection of ES3 and ES4 must be approximately as pleasant a
programming language as ES3 currently is.
No, the intersection is ES3 + reality + two (known)
On Nov 10, 2007, at 10:08 PM, Brendan Eich wrote:
On Nov 10, 2007, at 9:52 PM, Mark Miller wrote:
I'm using with here only as an example, to try to understand the
nature of the compatibility constraints on the ES4 process.
Compatibility imposes footprint costs, but it also creates a
