Try this code to see what is funny
int main()
{
char str[100];
int length=0;
printf("Enter a string: ");
gets(str);
length=stringLength(str);
printf("Total number of characters (string length) are: %d\n",length);
printf("Enter a string: ");
gets(str);
length=stringLength(str);
printf("Total number of characters (string length) are: %d\n",length);
return 0;
}
-----
This code should not even compile.
Quote:
run it but it work so i don't know where is worng.
What do you mean by 'work'? if it don't crash, ok. if it give correct answer, it is more astonishing.
stringLength
is missing half the logic. What are you doing with the result when you return from recursion?
Use the debugger to see exactly what your code is doing, pay attention to variables.
There is a tool that allow you to see what your code is doing, its name is
debugger. It is also a great learning tool because it show you reality and you can see which expectation match reality.
When you don't understand what your code is doing or why it does what it does, the answer is
debugger.
Use the debugger 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[
^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[
^]
Basic Debugging with Visual Studio 2010 - YouTube[
^]
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 find bugs, it just help you to. When the code don't do what is expected, you are close to a bug.