From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,82c2596e4584d057 X-Google-Attributes: gid103376,public From: msiso2@infos2.unilim.fr (OS2 User) Subject: Re: Ariane 5 Failure - Summary Report Date: 1996/07/26 Message-ID: <4t9svq$hs@limdns.unilim.fr>#1/1 X-Deja-AN: 170299754 distribution: world references: <31F629B8.5FFB@lmtas.lmco.com> <4t6kk7$p8a@goanna.cs.rmit.edu.au> organization: Universite de Limoges newsgroups: comp.lang.ada Date: 1996-07-26T00:00:00+00:00 List-Id: Dale Stanbrough (dale@goanna.cs.rmit.edu.au) wrote: : Ken Garlington writes: : "1. The limits of exceptions (they are only as good as what you can do : when they are raised)." : : Now I know what is meant when people say "exceptions can be expensive" :-). In fact, the most expensive is not exception but the misunderstanding of them. For me it is the /Ostrich complex/ : If you not see it, you imagine it not exist. (it is not true !) Exception is a report structure, if you specify how it is raise for each component you can : - use it as control. ( Se the sentence (1)) - evitate it with controls ( You must be 101% reliable ) - ignore it, Kill the process, Crash the rocket :-( : Dale -- Christophe Faure _______________________________________________________ | * # # ### # | | Christophe FAURE * # # # @ # @ # @ | | Tel :+33()55.45.72.32 * # # ### # | | Fax :+33()55.45.73.15 * | | * Laboratoire M.S.I | | e-mail : Faure@unilim.fr * Universite de Limoges | | * F-87060 LIMOGES | |_______________________________________________________|