RICHARD FERNANDEZ wrote:
No warnings? Hmmmm.... Are you sure your program actually ran
the new code? That should have generated at least one
warning. Is there any chance you've redirected or closed the
STDERR filehandle? You can always add a line like this during
development, if you need to be sure the new code is being
reached and that warnings are showing up:
warn "Yes; execution does reach this point";
Strange, I agree.
Immediately before your test code I have a line that reads:
print "Creating gzip'd archive\n";
and after the job runs, I definitely end up with a .gz file, just an
empty one.
I hate to do it, but I guess I'll have to shell out. Can't spend any
more time on this, unless anyone
else has any more ideas?
Thanks for looking at it, though. I appreciate it.
If you end up with a new, empty .gz file then the line
warn "File '$new_name' not created as expected"
unless -f $new_name and -s _;
will generate a warning. Are you seeing this?
Rob
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
