Pascal Chambon wrote: > (imo, most people just want to know if the operation was successful, I > don't know if many developers scan error codes to act accordingly). And as a user of applications written by those developers, it is a practice I detest with a passion. Debugging environmental problems is painful enough without further encouraging applications that lie to their users as to what has actually gone wrong. For example, a file not existing, a file being locked by another process, and the user not having write permissions to the file are problems that demand very different responses from the user. Applications that give the same error message for all three problems are far too common. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4