Subj : for - in  support
To   : netscape.public.mozilla.jseng
From : Oscar
Date : Mon Sep 27 2004 08:24 pm

Hi all, again...



I have looked a bit at the ECMA spec. and I believe that spidermonkey has a
defect in the for-in implementation.



12.6.4 of ECMA-262 which defines the for-in Statement states that "If a
property that has not yet been visited during enumeration is deleted, then
it will not be visited"




When trying to verify this part of the specification I used the following

script:

count = 0;

result = "";

value = "";



t = new Object();

t.one = "one";

t.two = "two";

t.three = "three";

t.four = "four";



for (var prop in t) {

   if (count==1) delete(t.three);

   count++;

   value = value + t[prop];

   result = result + prop;

}





which results in

value == onetwoundefinedfour

result == onetwothreefour



i would expect



value == onetwofour

result == onetwofour





Have i misunderstood something here or should I report to bugzilla?



(have searched for a similar bug there but haven't found anyone)



Best Regards

Oscar

.