Hi folks.
ECMA-402 lists default locale as an unspecified "implementation dependent
behaviour”.
In the absence of a specified default locale behavior, can we agree to a de
facto or best effort behavior to match the OS’s or browser’s locale and
language settings?
We’d like Safari and WebKit to
I don’t object to the idea of levels of severity when throwing an exception,
but I don’t think it will be sufficient to defend against attacks either.
An attacker that wants to infer information about the target VM or stop
execution in some target code at a point of inconsistent state will still
> The possible semantics of global lexical declarations was extensively
> explored by TC39 before we make the final design decisions for ES6. The
> scoping of global lexical declarations is something we spent many hours
> discussing over a span of several years, including:
To be fair, some p
> JSC has been trying to kill off the initialiser expression in the for(in)
> statement, but we've encountered a bunch of reasonably significant content
> that breaks with it disallowed (a particularly prominent one currently is
> http://battlelog.battlefield.com/bf4/), so we will be bringing ba
FWIW, JavaScriptCore provides automatic semicolon insertion after all do-while
statements in all contexts. We made this change for web compatibility,
mimicking a Firefox quirk.
Geoff
On Feb 8, 2011, at 11:53 AM, Dave Fugate wrote:
> Just to confirm, do-while iteration statements do in fact req
5 matches
Mail list logo
