Your code isn't working and you don't want advice like using -w and strict? -w and strict are recommended exactly BECAUSE you find many bugs with them a lot faster.

Clearly using strict is more effort and one might be tempted to not use it while rapid prototyping, but invariably in the debug phase you pay the price for that. There is no such excuse for -w

Also it might be easier to help you if you tell us how the output of this program differs from what you want. It might be obvious to someone who downloads and starts it, but not everyone will do that.