Remember that we can't see your screen, access your HDD, or read your mind - we only get exactly what you type to work with. So saying "so much error" without telling us what the error messages are, or what line(s) they are associated with means we know nothing about your problem, and can't help!
But I'll try and help you to help yourself.
There are two types of error: Compile Time, and Run Time.
Compile time errors occur when you try to compile your code and the compiler spits it out with file and line references - these are cause by your code using the wrong syntax (such as a missing close bracket perhaps), or spelling a variable differently in two places, or ... loads of reasons, all related to how your code was written.
These tend to be offered up to you as a list of problems with each having a message which describes what the compiler doesn't like, the file name it is in, and the line number it was found on.
Solution: edit the file, find the line (most editors will allow you to type CTRL+G then a lien number to "jump" to it) and read the line and a few above and below in conjunction with the message to see what the problem is. Repeat until you get a "clean compilation".
Run time errors occur only once you have got a clean compile - until that point the EXE file you need to run isn't built so these errors can;t be found yet!
The occur because you told your code to do something wrong, and the range of errors here is far, far broader that Compile time errors, because there are so many more mistakes you could have made. Sometimes these hava message and your app dies, sometime it just doesn't do what you wanted it to.
Solution: Complicated because compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.
So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.
Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input Expected output Actual output
1 2 1
2 4 4
3 6 9
4 8 16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
int Double(int value)
{
return value * value;
}
Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!
Submit an article or tip