You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and because Linux is very lenient in this regard, and gives you pretty much unbound freedom to use any "unreserved" in anyway you want - there could be a free substitute for Linux return code responses (i.e. you can use window's 13 on Linux too).
Minimum effort mode:
Just return anything but 0 for any failed operation. Example:
User wants to download game/file
User initiates a download
DD either successfully downloads and writes a file (transient errors in-between are ignored) or validates existing cache and finds no changes/up-to-date
DD returns with 0
If DD fails to successfully execute #4 (including even just failing at parsing cmd args) it returns with code > 0
The text was updated successfully, but these errors were encountered:
What problem is this feature trying to solve?
Because parsing stdout text is pain when you use DD as cli tool and not a lib.
How would you like it to be solved?
By returning more or less "standardized" return codes for successful or failed operations.
Have you considered any alternative solutions
I stand corrected, parsing stdout is a MASSIVE pain.
Additional Information
Old, as Earth, and a meaningless argument, but her we go:
Sure, there aren't, but there is an overlap:
and because Linux is very lenient in this regard, and gives you pretty much unbound freedom to use any "unreserved" in anyway you want - there could be a free substitute for Linux return code responses (i.e. you can use window's 13 on Linux too).
Minimum effort mode:
Just return anything but 0 for any failed operation. Example:
The text was updated successfully, but these errors were encountered: