in reply to Re: Re: uninitialized values for arrays suddenly appear
in thread uninitialized values for arrays suddenly appear

  1. Add use strict; to the top of your script, under the shebang line.
  2. Fix the errors that pop up.
  3. Fix the logic that depends on those errors.
  4. Come back to us if the error you originally posted about is still there..

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Replies are listed 'Best First'.
Re: Re(3): uninitialized values for arrays suddenly appear
by jerrygarciuh (Curate) on Sep 08, 2001 at 00:43 UTC
    OK I am using strict; and warnings; from now on. Under those conditions here is what happens- I get error #1 about 15 times because I am testing locally and the script is designed to search my site's files. Error #2 occurs for every var. What I guess I need to know now is how to record the errors the script produces when in situ on my server. Please advise me on how to do that, I assume that would need to be a sub in the script which writes the file for me? TIA
    jg
    error #1 "Variable "$FILE" is not imported at smappend.pl line 87."
    error #2 "Global symbol "$basedir" requires explicit package name at smappend.pl line 8."
[reply]

In Section Seekers of Perl Wisdom