| |||||||||||||
When the programmer is forced to handle return codesWhen the programmer is forced to handle return codesPosted Dec 5, 2009 8:00 UTC (Sat) by quotemstr (subscriber, #45331)In reply to: When the programmer is forced to handle return codes by cras Parent article: On the importance of return codes
If you get a signal, it means someone wants the process to be killed anyway, so might as well get on with it.There are many signals, only some of which are meant to kill processes. Consider job control. It's also perfectly legitimate (if a little antiquated) to use signals for reporting and miscellaneous functions. You don't want to leak a file descriptor upon receiving a nonfatal signal.
(Log in to post comments)
|
|||||||||||||