|
From: | Richard Frith-Macdonald |
Subject: | [bug #50031] libgnustep-base calls exit() |
Date: | Thu, 12 Jan 2017 10:39:02 +0000 (UTC) |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 |
Update of bug #50031 (project gnustep): Status: None => Wont Fix Open/Closed: Open => Declined _______________________________________________________ Follow-up Comment #1: I have reviewed the use of exit() and found all cases to be correct/necessary. Usage falls into four categories: 1. when the developer calls exit on the main thread ... the program must exit. 2. in the uncaught exception handler ... the program must exit 3. in a child after fork() where the subprocess can't be started properly 4. system startup failure before main() is entered (and therefore before any application developer code can handle Anything) _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50031> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |