In analyzer, catch use of continue and break in inappropriate places

tests/language/label_test.dart

Index: tests/language/label_test.dart
diff --git a/tests/language/label_test.dart b/tests/language/label_test.dart
index e9affb2cbc3b379a22eca96207867c7dcc6bb7bf..336664a9555a394e06f3036bcd9be6d4373e07fb 100644
--- a/tests/language/label_test.dart
+++ b/tests/language/label_test.dart
@@ -221,8 +221,10 @@ class Helper {
   }
 
    static test11() {
-     // Kind of odd, but is valid and shouldn't be flagged as useless either.
-     L: break L;
+     while (true) {

[Brian Wilkerson, 2012/06/08 18:49:05]

Looking at the spec, I don't see where the original version of this code is
disallowed. (That is, I don't see why we need the while loop wrapped around it.)

[zundel, 2012/06/08 20:15:08]

You are right. I had coded it incorrectly at first then when I found more
instances of this I went back and carefully re-read the spec and found out I was
wrong.

Reverted.

+       // Kind of odd, but is valid and shouldn't be flagged as useless either.
+       L: break L; 
+     }
      return 111;
    }