On Dec 9, 2007 7:03 PM, Stuart Moore <[EMAIL PROTECTED]> wrote: > Could the exit code used be determined by a flag? E.g. by default it > uses unix convention, 0 for any success; with an > --extended_error_codes flag or similar then it uses extra error codes > depending on the type of success (but for sanity uses the same codes > for failure with or without the flag) > > That should allow both of you to use it for scripting.
I like this idea. Like Micah said, there should _NOT_ be any return value non-zero in which the command was successful, even if it didn't download anything (if that's what we asked it to do, then it was successful). I think it would behoove us to have multiple return values for different *errors*, but not for different cases of success. I think this would be a very simple and helpful patch. (Well, "simple" may be an understatement because we'd have to go through every possible point of failure to create a return value.. mah.)
