Make invalid break/continue statements an early syntax error.

test/mjsunit/regress/regress-990205.js

Index: test/mjsunit/regress/regress-990205.js
diff --git a/test/mjsunit/regress/regress-990205.js b/test/mjsunit/regress/regress-990205.js
index 1ab5bf88b4252d475408e946808a557cfadbc90b..981e63f1b7e65c5c70875c696e739095ebd02d7c 100644
--- a/test/mjsunit/regress/regress-990205.js
+++ b/test/mjsunit/regress/regress-990205.js
@@ -25,11 +25,16 @@
 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+// We not throw syntax errors early for invalid break and continue

[Mads Ager (chromium), 2011/01/17 09:29:13]

We not -> We

[Lasse Reichstein, 2011/01/17 09:34:08]

Should have been "We now". Changed to just "We".

+// statements. The behavior has changed to make this a syntax error.
+// (Notice that the example isn't valid ECMAScript due to the 
+// function declaration that is not at top level.)
+
 function f() {
   // Force eager compilation of x through the use of eval. The break
   // in function x should not try to break out of the enclosing while.
   return eval("while(0) function x() { break; }; 42");
 };
 
-assertEquals(42, f());
+assertThrows("f()");