| Subject: | Allow consistency of handling failures |
When getting or putting a file, there are two different styles of failure notification. This can be a pain for those callers which would prefer just a single style of error-reporting and error-handling at the Net::FTP interface.
Failures at the remote end are generally reported in the form "(code, message)". But failures at the local end are generally of the form "carp message".
This proposal is based on a local modification we have had in place for a few years on a multi-petabyte archive. Have an option, settable in the "new" method, such that local failures can return as a simulated "(code,message)" style of error, consistent with remote failures. Then a caller setting this option need only handle a single style of error reporting.
1. Any thoughts why such an option would be a bad idea?
2. If it is deemed acceptable, I could supply the suggested patch as a first draft.