A summary of the discussion.
Pros:
-- current large implementations already satisfy this. I've tested it
on: Firefox 2, Firefox 3, Safari 3.2.1, IE6, IE7, the latest Opera,
SquirrelFish Extreme, TraceMonkey and V8.
-- It is powerful. When combined with a parser like Crockford's one
can
I use toString in a test suite that I built (jspec) to simplify the testing
DSL. Effectively, I extract the string contents of the function, and build a
new function with parameters representing some methods I want to make
available inside, and then call the function with those methods as
Hello!
Just wondering if anybody has any real world data lying around
covering what character encodings are necessary to support real world
script content. UTF-8, UTF-16 and ISO-8859-1 are a given guess. What
else?
--
David liorean Andersson
___
Hello!
I just noticed an inconsistency between the ES3 spec and browsers that
I've not seen discussed before. At the moment I'm on my iBook, so
these are not the most recent browsers, but they include ie5.2m, ff2,
saf1.3 and op9.5.
function fn(a, b, c, d, a, b, c, e){
liorean wrote:
[...]
10.1.3 Variable Instantiation
[...] If two or more formal parameters share the same
name, hence the same property, the corresponding property is given the
value that was supplied for the last parameter with this name.
Can anyone explain what the original rationale
On Sep 27, 2008, at 8:14 PM, David-Sarah Hopwood wrote:
liorean wrote:
[...]
10.1.3 Variable Instantiation
[...] If two or more formal parameters share the same
name, hence the same property, the corresponding property is given
the
value that was supplied for the last parameter
6 matches
Mail list logo
