VK wrote:
> > this is clearly defined behaviour
>
> By your books any stuff becomes His word as soon as it's spelled by W3.
> By my books a stuff *may* be a nonsense as long as it violates the
> end-used experience/expectations (see my definition of the "end-user"
> in the older topic).
>
> I'm really trying to love the Big Brother (W3) as much as I can. And
> I'm really sorry if I fail sometimes. I just have badly good memory I
> guess. In the particular I still remember that at the morning of the
> day the Buttle Of The 4th Versions began (which defined the winner of
> the Great Browser Wars) - W3 received just two links from Netscape and
> Microsoft: with a proposal to either download it and write standards
> from it; or to go to hell whatsoever. W3 even complained to ISA about
> it... An old story though...
>
> Also during my 15 years experience I've been learned that you never
> deal with standards. You always deal with particular engines build
> more-or-less upon these standards. Sometimes it does more than the
> standards promise, sometimes it does lesser than it should. The only
> right answer can be obtained from a test.
>
> P.S. The above discussed array behavior is fully ECMA-compliant.
Of course it's ECMA-compliant, and it does exactly as it's being told.
Nothing about the behavior described is at all what I or any other
programmer possessed of all his faculties should expect.
It was a logic error, not a language or implementation bug. Inspection
of the logic in the code makes that pretty clear, and it's either
[excess] laziness or [excess] hubris that obfuscates it.
When you redefine a variable, you should expect its old value to be
removed. Few languages (see also: PERL::Tie) behave otherwise, unless
you deliberately overload the assignment operator.
Look at the code again and actually step through what each line does.
You know. Debug it. Then point out exactly where the language is
behaving as it ought not, or not behaving as it ought, and why.
Received on Tue Oct 18 02:50:21 2005