in reply to Undef and Unitialized Issue

There are a number of issues with your code, but I'll focus on your uninitialized warnings question.

Have you tried adding any debugging print statements to help track down the problem?

Use the Data::Dump or Data::Dumper module to dump each of the vars in the statement that is generating the warning to verify they contain the values you expect. For each var that is undefined/uninitialized, trace it back step-by-step until you find where it began to be undefined. Adjust the code at that point to handle it, which could mean to assign a default value or it could mean that you should move to the next iteration.

Replies are listed 'Best First'.
Re^2: Undef and Unitialized Issue
by Pharazon (Acolyte) on Apr 02, 2015 at 14:46 UTC

    I mentioned in my post that I felt I had it tracked to a particular area of my code, however Athanasius pointed out a pretty obvious issue with that particular line which did resolve part of the problem. You can see my response to them for further details. I am however curious what issues there are with my code

    I'm not a perl programmer although having started working with the language I quite like it and will likely put some time into it going forward. It's just that the software packages we use in house are not capable of dealing with a file like this and so I was asked to come up with a solution and this is me trying to do that. Any advice is appreciated though if its very technical in relation to perl specific things it will likely be beyond me for the time being though I would still like to know.

    I know I can use the Datta::Dump to see what is going on but I have a loop that does something similar showing me the position in the 2d array as well since I was double checking positioning for the eventual output to csv format.