Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    Perhaps you can give some examples of the brittleness to watch out for? Such 'unspecified badness' is quite hard to spot until it's bitten you. Commented Sep 30, 2015 at 15:11
  • I think Bathsheba was simply trying to point out this kind of usage of break statement can be hard to follow when more loops are added and the code becomes larger and more complex, and I totally agree with him. Commented Sep 30, 2015 at 15:39
  • @ChristopherYang And I don't disagree: I can't actually remember the last time I used break with a label; I think that there are usually simpler ways to structure the code to avoid it. My point was that it would be useful to people who aren't familiar with the sorts of problems it creates to describe what is meant by saying that the code is brittle. Commented Sep 30, 2015 at 19:40