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=24737>. 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=24737 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2005-04-17 23:52 ------- I am not sure why "in both cases a null array would be expected." I see nothing in the documentation that would lead one to expect that result. In the case of an empty directory, it seems to me that an empty array is unquestionably the correct result. The case of a nonexistent file seems a bit more arguable, but I still think that a case can be made for an empty array. In any case, those are the results I get now. I don't get "No such file or directory" and a look through the code, which has changed since this bug was written, shows that such non-parseable input will now be discarded. I am changing the status of this bug, changing it to WONTFIX, although, as explained above, I don't really believe that returning a 0-length array is a bug in either case you mention. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
