Yes, Dave Herman already mentioned that, and I replied with this:
While this is true, this is far less of a problem than opt-in local
scoping, because the errors with opt-out local scoping are always going
to be local to the block/function the variable was assigned in.
Because of this, I believe
On Sep 5, 2008, at 4:33 PM, Ingvar von Schoultz wrote:
Ingvar von Schoultz skrev:
Mark S. Miller skrev:
On Fri, Sep 5, 2008 at 2:33 PM, Ingvar von Schoultz
[EMAIL PROTECTED] wrote:
and silent failures
are often very expensive to debug.
I don't understand. As currently proposed,
Brendan Eich skrev:
On Sep 5, 2008, at 4:33 PM, Ingvar von Schoultz wrote:
Another silent failure, much more expensive, is when you try
to write to non-writable properties. (And, apart from this,
also the related similar problem with constant variables).
This goes back to ES1. In Netscape's
On Fri, Sep 5, 2008 at 5:19 PM, Ingvar von Schoultz
[EMAIL PROTECTED] wrote:
Brendan Eich skrev:
On Sep 5, 2008, at 4:33 PM, Ingvar von Schoultz wrote:
This goes back to ES1. In Netscape's original JS implementation, I
reported an error which stopped the script on assignment to read-only
Brendan Eich wrote:
On Sep 5, 2008, at 5:19 PM, Ingvar von Schoultz wrote:
Can these properties be distinguished somehow? Then maybe the
bug can at least be limited to a few old properties.
Search through chapter 15 of ES3 for ReadOnly.
Thanks. Oops, I should have thought of that myself.
5 matches
Mail list logo
