Sigh. The code that iMalc posted was an equivalent of your (BROKEN!) for loop, to show you what was wrong with it. It was not a copy/paste source for a fix. Of *course* the program is still broke. Because you still haven't worked out what's broke in order to fix it despite iMalc given you a HUGE clue.
- Compiler warnings are like "Bridge Out Ahead" warnings. DON'T just ignore them.
- A compiler error is something SO stupid that the compiler genuinely can't carry on with its job. A compiler warning is the compiler saying "Well, that's bloody stupid but if you WANT to ignore me..." and carrying on.
- The best debugging tool in the world is a bunch of printf()'s for everything important around the bits you think might be wrong.
