DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30737>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30737 UnixFTPEntryParser returns null when timestamp is between 12:00am and 12:59am ------- Additional Comments From [EMAIL PROTECTED] 2004-09-15 02:37 ------- You raise an interesting point. I still don't agree with it. While I see merit in your claim that having arrays with null members is not a good thing, there are similar problems also inherent in "incomplete" objects. The uninformed user may just as well stumble on NPEs when dereferencing a non-existent date in a partially complete FTPFile, for example. The null member, while obviously not a perfect solution, does announce itself reasonably loudly, is easily detectable by the user, and that has value. Throwing an exception over the whole list might be too draconian a penalty for one unparsed listing out of a hundred. Thus, the current implementation is a reasonable compromise, I think. Our goal remains to have parsers that handle every conceivable case, even if that is almost impossible to achieve given the wide array of implementations out there. We are getting there, asymptotically. Your point about the return value of listFiles() not being documented to warn the user of this possibility is a valid one and I have now corrected it, both in FTPClient.listFiles() and in the mehtods of FTPListParseEngine on which it depends. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
