On Sat May 26 16:44:40 2012, kryde wrote:
In Net::FTP version 2.77, when doing a put() if there's an error from
read() it seems to be silently treated as normal eof, where I hoped it
would gives some sort of error.
I see the code notices an error from binmode(), or socket write() and
close(), and gives an undef return, but apparently not for read()
trouble.
The foo.pl below simulates a read error with a tied file handle.
I wonder if the $ftp->put() could return undef in this case.
In Net::FTP version 2.77, when doing a put() if there's an error from
read() it seems to be silently treated as normal eof, where I hoped it
would gives some sort of error.
I see the code notices an error from binmode(), or socket write() and
close(), and gives an undef return, but apparently not for read()
trouble.
The foo.pl below simulates a read error with a tied file handle.
I wonder if the $ftp->put() could return undef in this case.
to complete on either of two platforms at my disposal.
On Darwin/PPC, the program dies here:
#####
Cannot connect: Net::FTP: connect: Invalid argument at 113390_foo.pl
line 24.
#####
On Linux/i386, the program dies here:
#####
Cannot cwd: /pub: No such file or directory
at 113390_foo.pl line 30.
#####
Can you (or anyone) supply a different example?
Thank you very much.
Jim Keenan
---
via perlbug: queue: perl5 status: new
https://rt.perl.org:443/rt3/Ticket/Display.html?id=113390