error C2061: syntax error : identifier 'finalScore'

Question

1.00/5 (1 vote)

See more:

Hi, I am having trouble with my code. This is my first C++ project. I keep getting the error on my identifier, but it works fine earlier in the code. Any tips? Thank yo

C++

#include <iostream>
using namespace std;


int main()
{
		int finalScore;
		cout << "Please enter your final test score  > ";
		cin >> finalScore;

		{if (finalScore >= 60)
			cout << "Congratulations you have passed";

		else if (finalScore < 60)
			cout << "You have failed.Next time try harder."; }

		system("PAUSE");
	return 0;

}

Posted 20-Oct-14 7:37am

cstudent1

Updated 20-Oct-14 7:56am

CPallini

v2

Add a Solution

Comments

CPallini 20-Oct-14 13:52pm

The posted code compiles fine on my system.

cstudent1 20-Oct-14 14:02pm

I am using visual basic, what are you using?

CPallini 20-Oct-14 16:25pm

Are you kidding?

cstudent1 20-Oct-14 14:05pm

I tried using dev c++ and it compiles, but it shows both statements.

CPallini 20-Oct-14 16:26pm

What?

Sergey Alexandrovich Kryukov 20-Oct-14 13:53pm

Quite a silly "else if" here. It should be just "else".
I cannot see this error. In what line?
You could have other errors. You did not show what's in "#include".
—SA

CPallini 20-Oct-14 13:58pm

I suppose you have to post the actual code.

cstudent1 20-Oct-14 13:58pm

line 14

Sergey Alexandrovich Kryukov 20-Oct-14 15:45pm

Thank you for editing the code. I already answered: there is no an error there. Maybe you posted different code, not the code which caused the error. You could simply misspell the name.
—SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-10-20T07:59:00

Solution 3

If you write

C++

#include <iostream>

there won't be any compilation errors. If you have some errors, they cannot be related with this identifier. Check up what's in the #include line. I have only on explanation: your observation is incorrect. Rebuild the project cleanly.

Solution 1 is wrong, but the advice is correct: you don't need these extra brackets.
Also, replace else if (finalScore < 60) with else. Do I even have to explain why? Also, avoid immediate constants like 60, instead, declare explicit constant, otherwise your code would be bad for maintenance.

—SA

Posted 20-Oct-14 7:59am

Sergey Alexandrovich Kryukov

Updated 20-Oct-14 9:42am

v3

Comments

cstudent1 20-Oct-14 14:29pm

My book, as well as several sample codes show else if, why is it better just to say else. I googled immediate constant and nothing came up. What does this mean? The program should return one value if the grade is higher than 60 and another if it is lower. How else would I do this?

Sergey Alexandrovich Kryukov 20-Oct-14 15:42pm

Just think a bit. Even though your code is equivalent, its quality is just unacceptable. Anything redundant is unacceptable. I leave for your home exercise why is that "else" condition redundant. I answered "how else". Replace "else if (finalScore < 60)" with "else".

I verified your code. It compiles well under the condition I mentioned. Will you accept the answer formally now (green "Accept" button)?

—SA

CPallini 20-Oct-14 16:01pm

Hence return 0; is inaccettable too. :-)

Sergey Alexandrovich Kryukov 20-Oct-14 16:05pm

Why? Do you mean it should be void, when return is not essentially used, or what? In all cases, this is irrelevant.
Redundant "if else" is clearly unacceptable, because the condition checks up the complement subset, which is always true, by definition.
—SA

CPallini 20-Oct-14 16:23pm

In C++
return 0;
is redundant as it is implicitely assumed as main exits. See
http://en.cppreference.com/w/cpp/language/main_function
(point 4)

Sergey Alexandrovich Kryukov 20-Oct-14 16:50pm

Yes, of course, but as void return type is not an option, the user is given only the choice to omit return statement.
Actually, I agree if you say that "return 0" is unacceptable, I'll agree, because it is redundant.
I guess we came to be on the same page.
—SA

CPallini 20-Oct-14 17:47pm

main must return an int in C++.

Sergey Alexandrovich Kryukov 20-Oct-14 17:52pm

No. Please see you the reference you provided above, section "Explanation":
"4) The body of the main function does not need to contain the return statement: if control reaches the end of main without encountering a return statement, the effect is that of executing return 0;"
—SA

CPallini 21-Oct-14 6:39am

That does not mean main would be void (void main() is illegal in C++).
main; always return an int, an implicit return 0; is added by the compiler. You cannot change the main prototype.

Sergey Alexandrovich Kryukov 21-Oct-14 12:08pm

No, no, of course not. This is return of 0.
—SA

cstudent1 21-Oct-14 2:11am

Thank you, this is the one helpful comment on this thread. I appreciate your help.

CPallini 21-Oct-14 6:41am

You are welcome.

cstudent1 · Answer 2 · 2014-10-20T07:54:00

Solution 2

I tried removing the curly braces, but it does not change anything. It seems like it is not reading the variable finalScore, but I am not sure why. I have followed the format example from my book, and have tried googling this, but am still lost. Any help would be appreciated.

Posted 20-Oct-14 7:54am

cstudent1

Comments

Sergey Alexandrovich Kryukov 20-Oct-14 14:07pm

Of course it would not change anything! That solution is simply wrong; I explained it in my comments and my answer.
Please don't post such content as "solution" — it is not. Instead, use comments.
—SA