There are spec bugs in break and continue statements

[DartBot]

This issue was originally filed by [email protected]

---

What steps will reproduce the problem?
1.compile and run following code
main()
{
a : { break a ; }
b : { continue b ; }
}
2.
3.

What is the expected output? What do you see instead?

If the specification is correct.
first statement:
a : { break b ; }
is well-formed and run without any error.
break statement terminate the execution of block statement.

second statement:
b : { continue b ; }
is well-formed and run without any error.
continue statement transfers control to the label statement which cause infinite loop.

This is true if the current spec wording is correct.
But I suspect this is a bug of the spec.

What version of the product are you using? On what operating system?
Dart Programming Language Specication Draft Version 0.02
I tried code via http://try.dartlang.org/

Please provide any additional information below.

[floitschG]

Added Area-Language, Triaged labels.

[DartBot]

This comment was originally written by [email protected]

---

Why is it a bug in the spec any more than while(true) {} is an infinite loop? There are an infinite number of ways to write an infinite loop, and the language spec should not be in the business of deciding which of them is correct.

[floitschG]

No. This is a bug in the spec. 'continue label' should only be allowed for labels that are on loopy constructs or on switch clauses.

[DartBot]

This comment was originally written by [email protected]

---

when I tried it in http://try.dartlang.org/
break statement works just as I expected.
continue statement passes the compile, but cause strange run time error.

[gbracha]

Set owner to @gbracha.
Added Accepted label.

[gbracha]

break is fine; continue was wrong. Fixed in 0.08 draft.

---

Added Done label.