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,63ceef1cf4561e32 X-Google-Attributes: gid103376,public From: Kieran Mckey Subject: Re: Customer balks at Ada -- any hope? Date: 2000/07/19 Message-ID: <3975C9C0.E524CBB@baesystems.com>#1/1 X-Deja-AN: 648233988 Content-Transfer-Encoding: 7bit References: <8l01s4$gnr$1@nnrp1.deja.com> <8l2pqo$im7$1@nnrp1.deja.com> <5dtGPVPqfHh5@eisner.decus.org> <39755FB0.81586D45@baesystems.com> <8l40kb$7na$1@xs4.xs4all.nl> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Trace: 19 Jul 2000 16:28:31 GMT, rc2954.rochstr.gmav.gecm.com MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-07-19T00:00:00+00:00 List-Id: Ken Garlington wrote: > > "fdebruin" wrote in message > news:8l40kb$7na$1@xs4.xs4all.nl... > > Kieran Mckey writes: > > > > >compiler switches. You should design the system so that the code will > > >meet performance requirements regardless of whether run-time checks are > > >enabled or not. > > > > > Sometimes, you don't have that luxury. > > That is very true Frank, I've been on projects where RTC was turned off to meet performance targets. All I am saying is that IMHO this is poor engineering practice and the issue should be considered during initial system design. > > Don't forget another aspect of run-time checks that is particularly > important to embedded systems: Run-time checks are completely worthless... > unless you have a proper course of action to take when they occur. > That is right. A proper course of action may be just logging the event in a non-volatile store (admittedly not much use when this blows up !) or you could attempt some error recovery. Personally, I think Ada could be better in the area of exception handling, it still being a rather crude Goto at the moment, is there no way of informing the caller that an exception has occurred in the sub-program except to re-raise the exception ? Kieran Mckey