Index: test/webkit/for-in-var-scope-expected.txt |
diff --git a/test/webkit/concat-while-having-a-bad-time-expected.txt b/test/webkit/for-in-var-scope-expected.txt |
similarity index 80% |
copy from test/webkit/concat-while-having-a-bad-time-expected.txt |
copy to test/webkit/for-in-var-scope-expected.txt |
index f949db98fd7b911d30b20281c82ee0f801405c77..1f66d8a40f7d626a0c7155b3a1e4d3d77d8ea61a 100644 |
--- a/test/webkit/concat-while-having-a-bad-time-expected.txt |
+++ b/test/webkit/for-in-var-scope-expected.txt |
@@ -21,12 +21,13 @@ |
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS |
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
-Tests the behavior of Array.prototype.concat while the array is having a bad time due to one of the elements we are concatenating. |
+This tests that for/in statements properly scope a variable that's declared in one. In previous versions of JavaScriptCore there were two bugs that caused problems. First, the loop variable declaration would not be processed. Second, the code to set the loop variable would incorrectly walk the scope chain even after setting the loop variable. |
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". |
-PASS [42].concat() is [42] |
+PASS i is 'start i' |
+PASS j is 'propName' |
PASS successfullyParsed is true |
TEST COMPLETE |