Re^3: How to avoid "Use of uninitialized value" with printf?

Just wanted to report back to advise that I've now got this aspect of things working the way I wanted, with your help.

I've also gone back over my code and tidied things up a bit and removed some of the superfluous variables I was using for reading in files, and gone back to using the default $_, which made things neater and has helped me to work out a couple other kinks.

So, thanks again one and all for your assistance and suggestions :)

Comment on Re^3: How to avoid "Use of uninitialized value" with printf?

Replies are listed 'Best First'.
Re^4: How to avoid "Use of uninitialized value" with printf? by GrandFather (Saint) on Apr 12, 2012 at 07:43 UTC
To use or not to use $_ is often a hard call in the sense that there is often not a compelling reason to choose one technique over the other. However, I tend to use named variables in preference to uses of the default variable where the usage spans more than one statement. The default variable doesn't convey any sense of the use it is being put to whereas a well named variable can add a great deal to understanding code. "Neater" can mean a great many things, but "long term maintainable" is generally a much more desirable objective. True laziness is hard work	[reply]

Replies are listed 'Best First'.

Re^4: How to avoid "Use of uninitialized value" with printf?
by GrandFather (Saint) on Apr 12, 2012 at 07:43 UTC

To use or not to use $_ is often a hard call in the sense that there is often not a compelling reason to choose one technique over the other. However, I tend to use named variables in preference to uses of the default variable where the usage spans more than one statement. The default variable doesn't convey any sense of the use it is being put to whereas a well named variable can add a great deal to understanding code.

"Neater" can mean a great many things, but "long term maintainable" is generally a much more desirable objective.

True laziness is hard work

[reply]