On Sun, Feb 15, 2004 at 09:43:23PM +0100, Matthias Urlichs wrote: > Every error whatsoever throws an exception. That's far better from a > quality POV than to check the error return of _every_single_statement_, > because (a) nobody actually programs that way, and (b) if you actually do > program that way your code will be twice as long and ten times as > unreadable. However, it results in code that throws exceptions to the user rather than useful error messages, which is amateurish. The user should never see an exception unless there is a bug in your code; errors from the system should be handled properly. This *does* make your code twice as long, but it will not make it any less readable if you do it right. Failing to do it is like failing to test your code before releasing it, or trusting data read from the network - it is not something that has any place in a serious program. "Python makes it easier to write bad code" is a pretty lousy argument. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- |
Attachment:
signature.asc
Description: Digital signature