The great big fat hints you should have seen and pondered were: Use of uninitialized value in transliteration (tr///) at noname.pl lin +e 9, <DATA> line 1. Use of uninitialized value in concatenation (.) or string at noname.pl + line 10, <DATA> line 1. download Note that I used a __DATA__ (see the Special Literals sub-section) section rather than using an external file for the test code so the line numbers will differ somewhat from yours.
I, in fact, do pay attention to output when I have strictures in play. My problem is with the interpretation of much of strictures output, which I sometimes find difficult. I'm sorry, however, to have neglected to post that output... I'll do better next time.
With regard to the reference to using __DATA__ ...
I followed up with reading the recommended Special Literals sub-section. It appears to be a very useful tool for script portability and testing. Thanks, for that bit of information!
One question, though, regarding the use of __DATA__, when a script requires two or more sets of data. How would one, then, represent and call upon the subsequent sets?
Thanks, again!
In reply to Re^2: Problem using transliteration to modify a variable...
by cgmd
in thread Problem using transliteration to modify a variable...
by cgmd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |