Before school ended, I donated some of my time to helping out the Intro to Java kids. In that class, I realized that when you tell beginning programmers “End each line with a semi-colon,” they think you really mean it. As in, every single line with actual code (e.g. not brackets) must end with a semi-colon. Well, it’s sad news but that is not true. Not every line needs a semi-colon.
Here’s an example. Look at this code. I dare you even to try running it. You’ll end up with an error.
public static void main(String[] args) {
int magic = 10;
if (magic < 20);
{
System.out.println("weak magic");
}
else
{
System.out.println("strong magic");
}
}
The error is of course, uncommunicative of the true problem. Did you spot the error yet?
syntax error on token “else”, delete this token
The problem here isn’t the else or even the if. No, the problem is a semi-colon. Seriously. Take a look at the if-statement expression. The oddity comes about when you actually see the semi-colon attached to the end of it. And because the if-statement ended there, the else has no preceding pair so it has no choice but to error out.
This example is actually a clear cut case of putting a semi-colon after an if-statement expression. Imagine you didn’t have an error to remind you what you just did. You might just have a plain statement and proper following brackets.
public static void main(String[] args) {
int magic = 10;
if (magic < 20); {
System.out.println("weak magic");
}
}
Without the else to throw an error message up, how easy would this be to spot? It’s tricky. What if your if-case was a rare edge case condition that you were hard pressed to demonstrate in testing but you theoretically knew it existed? You’d almost never know this wasn’t work until your nuclear reactor began to melt down.
The moral of story: kids will do what you tell them and mind you semi-colons at the end of constructs.