Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.programming Subject: Re: etiology of exceptions Date: Tue, 09 Oct 2012 10:46:00 +1300 Lines: 24 Message-ID: References: <902b53ef-fa30-4470-914f-a5d3bf904b60@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net oOuiLAhpJZoyZal0uMw7NAZasP/4kmP8qf3f2lfeaME5JGykvM Cancel-Lock: sha1:qcPt+4PE9TiBzqf7fF858NMW9gQ= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:12.0) Gecko/20120423 Thunderbird/12.0 In-Reply-To: Xref: csiph.com comp.programming:2297 On 10/09/12 10:37, LudovicoVan wrote: > wrote in message > news:902b53ef-fa30-4470-914f-a5d3bf904b60@googlegroups.com... >> tiistai, 25. syyskuuta 2012 17.29.21 UTC+3 bob kirjoitti: >>> What is the etiology of exceptions? Did they come about because people >>> got tired of having to check a return value every time they called a >>> function? >> >> Not answering the etiology of exceptions question, sorry. But a related >> question: What is the best understanding of their role after 40+ years? >> Let me try: >> >> -exceptions for programmer errors only >> -exceptions should be reserved for complete failures >> -exception are no program flow cotrol structures >> -exception do not add to program correctness, but to robustness (operation >> out of specifications) > > Not so. Now there's a well presented argument..... -- Ian Collins