Error - but I can't find it!!

[Dan_]

I'm using DevC++ to write this and I have to write it in C. My problem is when I try to compile I get a red line that the very top of my code, and it's red, not the maroon red, and then it says on line 28 I have a syntax error before the { token - this line is maroon. I am a beginning programmer and am working through this program doing the basic parts first, therefore my code is not entirely complete, but from the functions I have there now, it should be able to compile. If you could help me find the error(s) I'd greatly appreciate it! The code is attached as the text doc.

Thanks.

[wtd]

There are many, many problems with this code. The Hungarian notation and extraneous commenting are big problems.

However, your program would compile but for two things, as far as I can see, without actually trying to compile it myself.

So... anyway... the error it's telling you about is on line 28. What is on line 28?

[md]

I count four errors, and all of them are exactly the same; they probably aren't the same one's wtd found though. I too have not tried compiling it.

It'd be best if you post the actual error the compiler gives you, not the color your IDE highlights the line in. If you read the compiler's error message it'll probably tell you exactly what's wrong

[Dan_]

The excessive amount of commenting is because I lost points for not commenting enough on the last one. :\ And the error line it was giving me was: elseif (iInput == 2) {

I realize I needed it as else if*

Thanks guys, it's compiling now. Now I need to finish up the coding so it does what it needs to do! And I also added a ; after the abort()

Appreciate the help!

[wtd]

Dan_ wrote:

The excessive amount of commenting is because I lost points for not commenting enough on the last one.

If those kinds of comments get you better scores, then your teacher loses major points for being a moron.

Comments should never be used to tell the person reading the code something the language itself tells them.

[Tony]

commenting is used to tell why you are doing something, not what. The what part is the code itself.