Paul Clapham wrote:
Chris Smithtopher wrote:The example above is from Boyarsky and Selikoff, and iirc they don't take a particular stance on whether they're good or bad. More like "Here's a thing you might see, here's how it's used, but it's up to you.
If feature X is defined to be one of the Java features covered by the exam, then you have to learn it. There's lots of features which are disliked by various people for various reasons (my personal dislike is having to learn the difference between x++ and ++x) but those dislikes are all irrelevant, they're on the exam so you have to learn them. After all in your future day job you might encounter one of those unlikeable features in code written by somebody else and you'd have to understand how it works.
I'm re-reading this section at the moment, since nested loops are a bit of a weakness for me, and it turns out the labels are NOT on the exam, but it looks like they use them kind of a lot in this section in order to help visualize and clarify how the loops work, and what will happen with a labeled and unlabeled break statement.
On the one hand, it does help clarity a bit, but on the other hand, if it's not on the exam and most people don't use them, the amount of time spent on them seems a smidge excessive.
Like I said before, though, better to know about them then be surprised irl.