if / else errors - learn how to fix these | Codecademy (2024)

points

Submitted by

Judy

If you have a question that isn’t answered here, please use the green “Ask a question” button. Copy/paste all of your code in with your question, include the exercise number you are working on and the exact error message you are seeing.

Typically the following error messages are caused by faulty if/else syntax

• “syntax error”
• “missing operand; found else”
• “Unexpected token else”
• “expected an identifier and instead saw “else”“

First off, a quick review of what if statements look like.

A typical if () statement looks like this. Depending on what you are checking for, the else if and else blocks may not be needed. Note how the { }, ( ) and ; are used.

if (this condition is true) { do something;} else if { do this other thing;} else if { do this awesome thing;} else { do something different;}

Do a quick check to see if you haven’t misspelled or mis-capitalized if or else.

Using any of these is going to earn you an error: IF, If, ELSE, Else

All good with your spelling and capitalization?Okay, on to the next check.

Is there an indicator complaining about your else?

In JavaScript semicolons mark the end of statements.

When you put a semicolon at the end of a condition, like this: if (choice1 === choice2); you are telling the interpreter to consider that as the end of your if statement. Any code following that will be processed without regard for the outcome of that if condition.

If you are getting an error about the else it is because you’ve told the interpreter that the ; was the end of your if statement so when it finds the else a few lines later it starts complaining.

A few examples of where not to put a semicolon:

if (age < 18);if ( 9 > 10 );if ("Yogi Bear".length < 3);if ("Jon".length * 2 / (2+1) === 4 );if (userAnswer === "yes");if (feedback > 8);if (income >= 100);

I think you can see what I’m getting at.

Checked for all those and still haven’t found the bug yet?

Have a look and make sure you don’t have any semicolons on your else or your else if ( ), doing that will also end your if statement sooner than you had planned.

These are both going to give you errors:

} else if (computerChoice < 2/3); {else;

Curious about other situations where semicolons should be used/not used?

34

votes

else is not allowed to have a condition

@AlbionsRefuge - Great post!!

I’ve also noticed a few people trying to do things like…

if ( a < b) { do something here;}else if (a > b) { do this other thing;}else (a == b) { do something different;}

and then they post a question asking what is wrong with their code.

It seems that they aren’t grasping a few concepts about the flow of logic in if / else if / else statements.

So I thought this would be a great place to point out a few things that those struggling with if / else if / else might find helpful.

For one thing, unlike if and else if, an else statement is not used to do condition checking. The purpose of else is to execute alternative code in the situation where the if, and else if conditions return false.

In the particular code example above, if the program execution has reached the else statement it means that:

a < b returned false and a > b also returned false.

If the value of a is: not greater than the value of b and not less than the value of b, then it logically follows that the value of a must be equal to the value of b! because there is no other option for what the value of a could be.

There is no need to even bother trying to test for ( a == b ). You simply have the else statement do something.

The correct code would be:

if ( a < b) { do something here;}else if (a > b) { do this other thing;}else { do something different;}

I think those of us who are seasoned programmers (or people like me who have just had some exposure to programming concepts and have coded up a few personal projects) tend to take these things for granted.

Pointing them out might seem very elementary to experienced programmers. However, beginners who have never dealt with these concepts can and do struggle with these kinds of ideas and I felt a good explanation might be in order.

I hope this is a helpful comment!

over 10 years

Judy

over 10 years

Mark

over 10 years

chrismc1076

over 10 years

KhalilDaCoder

over 10 years

宇峯鄭

over 10 years

Trenton Turner

over 10 years

MUSTAPHA OLUWATOSIN

over 10 years

Anoosh Moutafian

over 10 years

Ben Barber

over 10 years

Alexander Scheer

over 10 years

Emily Owaki

about 10 years

Goutam Bagchi

about 10 years

Appear

about 10 years

total_tool_22

almost 10 years

haxor789

almost 10 years

Gatho5

almost 10 years

George

almost 10 years

RonandoL

over 9 years

Grady Lawlor

about 9 years

sweginator3000

about 9 years

link110

about 9 years

Ron Harrington

almost 9 years

Judy

almost 9 years

haxor789

almost 9 years

Christopher mlalazi

almost 9 years

12

votes

Conditions, Blocks and Semicolons

The most simple conditional statement (1) looks like this:

if(condition) statement;

Here statement is exactly 1 statement. In case you want an alternativ to the if you can extend it with an else (2):

if(condition) statement;else statement2;

Again statement and statement2 are only one statement (each). But what about using more than one statement in a case? (3)

if(condition) statement1; statement2;

here statement1 would belong to the condition and statement2 would be executed without condition. (4)

if(condition) statement1; statement2;else statement3;

And here it would get even worse, as the else needs to follow directly after the statement of the if or they will not be treated as connected and you get an error as an else doesn’t make sense without an if.

So how can we use more than one statement per case, what are these {} we usually use and why should we even bother about these cases mentioned above?

Well to have more than one statement per case we use the trick of working with blocks of code which start with { and end with } these blocks count as one statement regardless of the number of statements which are inside.(*)

The reason why we should have a look at this although you could be perfectly fine by using blocks all the time even if they are not necessary is that we every now an then may encounter one of the errors described above which are related to this ability.

e.g. a semicolon:

When you put a semicolon at the end of a condition, like this: if (choice1 === choice2); you are telling the interpreter to consider that as the end of your if statement. Any code following that will be processed without regard for the outcome of that if condition.

That’s pretty close, but the semicolon doesn’t end the if statement itself, it ends the statement of the if. This might be confusing, but have a look at (1) and you could see that if(condition); just means:

if(condition) /*empty space*/;

so the semicolon creates an empty statement by ending the “nothing” after the condition which would normaly be ignored and now the condition is either finished or an else needs to follow directly after it, but mostly it was just a mistake and it goes like this: if(condition);{...} and then you end up at the error described in (4).

Another use of this feature is that a conditional statement counts as one statement aswell, which lets us create an else if case by nesting:

if(condition) statement;else if(condition2) statement2; else statement3;

could be formatted to:

if(condition) statement1;else if(condition2) statement2;else statement3;

(*) {} are used as blocks of codes for conditions and loops, functions and objects may use them in a different way.

over 10 years

KhalilDaCoder

over 10 years

Jiajia Montrasio

about 10 years

Goutam Bagchi

about 10 years

kowhai9t9

almost 10 years

vicente lee

almost 10 years

Mileslogic

over 9 years

4

votes

almost 11 years

JovyCB

over 10 years

Judy

over 10 years

Wanda

over 10 years

Judy

over 10 years

Wanda

over 10 years

Judy

over 10 years

darecode

over 10 years

Judy

over 10 years

darecode

over 10 years

Judy

over 10 years

darecode

over 10 years

http://www.codecademy.com/forum_questions/52e463bb548c355a72005f55 @AlbionsRefuge

Judy

over 10 years

darecode

over 10 years

Mineli

over 10 years

Mineli

over 10 years

var balance = 20.97;

// Complete the condition in the ()s on line 4if (balance<10 ) { console.log( “balance-5”);} else { }console.log(“ balance”);

Judy

over 10 years

Mineli

over 10 years

Judy

over 10 years

Ben Barber

over 10 years

haxor789

over 10 years

alaskalynn

about 10 years

13AlphaWolf13

over 9 years

haxor789

over 9 years

nicoledille

about 9 years

Judy

about 9 years

votes

over 10 years

Judy

over 10 years

Brian Archer

over 10 years

votes

@Mark: The error you explained is also caused by this only-one-statement-after-a-conditional-case-rule. At first you are absolutly right about the fact that else does not need a condition! But the error in the code is not that else has “condition” but that there are two statements on one line (without separator):

else (a == b) { do something different;}

first statement is the a == b, which is a pretty pointless statement as it is just true or false and is neither stored nor printed (as said, else doesn’t expect a condition, so the () don’t show any relation to else but just increase the priority of evaluating the stuff inside, which is unnecessary as this code would follow anyway) and the second statement is the begining of the block.

So if you had used:

else (a == b) { do something different;}

or

else (a == b); { do something different;}

it would still be pointless and missleading as the code in the block would be evaluated in any case, but syntactically it would be correct.

over 10 years

votes

var sleepCheck = function(numHours) { if (numHours >= 8) { return "You're getting plenty of sleep! Maybe even too much!"; } else { return "Get some more shut eye!; }};sleepCheck(5);

SyntaxError: Unexpected token ILLEGAL

almost 9 years

Judy

almost 9 years

votes

almost 9 years

Judy

almost 9 years

votes

Hey, i’m not sure what’s wrong with the code. The error I’m getting is “unexpected token else”

var compare = function(choice1, choice2) { if (choice1 === choice2) { return “The result is a tie!”; } else if (choice1 === “rock”) { if (choice2 === “scissors”) { return “rock wins”; } else { return “paper wins”; } };

 else if (choice1 === "paper") { if (choice2 === "rock") { return "paper wins"; } else { return "scissors wins"; } };

};

PS: I’ve figured it out. I only needed that final semi-colon after the last closing brace, not the ones after the else if closing brace.

over 8 years