Fix V8 bug 1084

test/mjsunit/strict-mode.js

Index: test/mjsunit/strict-mode.js
diff --git a/test/mjsunit/strict-mode.js b/test/mjsunit/strict-mode.js
index 6f3a2441342d24541202e78b6d8729c1cd989c9f..e6922c59b46bbb0ebf86147e573b63804f9a10b9 100644
--- a/test/mjsunit/strict-mode.js
+++ b/test/mjsunit/strict-mode.js
@@ -150,6 +150,12 @@ CheckStrictMode("'Hello octal\\032'");
 CheckStrictMode("function octal() { return 012; }");
 CheckStrictMode("function octal() { return '\\032'; }");
 
+function ValidEscape() {
+  "use strict";
+  var x = '\0';
+  var y = "\0";
+}
+

[Lasse Reichstein, 2011/01/31 06:05:19]

If the preparser marks this function as lazy (which it will), the body won't be
parsed by the parser at all. In that case, even if there was a strict-mode
syntax error, I'm not sure it would be thrown.
You need to call the function to be sure that it's parsed.

(We should probably add checks to the preparser too, to ensure that we make it
an early error).

[Martin Maly, 2011/01/31 22:44:06]

Done. The pereparser work is on my todo list.

 // Octal before "use strict"
 assertThrows('\
   function strict() {\