Quote:
I have unwanted number "200" at the end in console.
You forgot to tell us what is wanted, so we can only guess.
By design you code print the last result of multiplication table after the table.
This code is simple enough to be a good candidate for debugger learning.
There are 2 reasons to learn debugger:
- You learn ways to find bugs by yourself.
- you improve your understanding of code and thus your learning curve.
-----
Your code do not behave the way you expect, and you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
Debugger - Wikipedia, the free encyclopedia[
^]
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jdb.html[
^]
https://www.jetbrains.com/idea/help/debugging-your-first-java-application.html[
^]
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.