Clean up and update const / var

test/mjsunit/regress/regress-global-freeze-const.js

Index: test/mjsunit/regress/regress-global-freeze-const.js
diff --git a/test/mjsunit/regress/regress-global-freeze-const.js b/test/mjsunit/regress/regress-global-freeze-const.js
index 0b9e1f3ebd4bb79c00db30a7b33e450e5bfe68a0..c5ac98667fefbb3d065675cc007b6aed4cd6e2f7 100644
--- a/test/mjsunit/regress/regress-global-freeze-const.js
+++ b/test/mjsunit/regress/regress-global-freeze-const.js
@@ -2,6 +2,6 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-__defineSetter__('x', function() { });
+Object.defineProperty(this, 'x', {set: function() { }});
 Object.freeze(this);
-eval('const x = 1');
+eval('"use strict"; x = 20;');

[rossberg, 2014/07/11 12:54:49]

Removing the const makes the name of this test obscure. Instead, maybe assert
that the original eval throws now?

[Toon Verwaest, 2014/07/14 07:39:56]

Changed the name of the file to indicate its meaning.
I had adjusted the code to ensure it keeps testing what it was supposed to.

On 2014/07/11 12:54:49, rossberg wrote:

[rossberg, 2014/07/14 12:04:22]

Hm, I think it really was supposed to test const's behaviour. We changed that
behaviour now, so I think it's more adequate to adjust the test expectations
rather than to test something different. Or have both.