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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e6d1607a5397de6b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2000-11-01 06:52:04 PST Path: supernews.google.com!sn-xit-02!supernews.com!bignews.mediaways.net!ams-newsfeed.speedport.net!ldn-newsfeed.speedport.net!newsfeed.speedport.net!newsfeed.icl.net!news.maxwell.syr.edu!newsxfer3.itd.umich.edu!news2.acs.oakland.edu!jobone!dailyplanet.srl.ford.com!eccws12.dearborn.ford.com!not-for-mail From: John Kern Newsgroups: comp.lang.ada Subject: Re: Is the Ada World Embarrassed by the Defense Industry? Date: Wed, 01 Nov 2000 09:38:50 -0500 Organization: Visteon Coropration Message-ID: <3A002AFA.910DC18E@NOSPAM.visteon.com> References: <39FDE9E4.35F615A6@netwood.net> <39FDF025.FDDE904F@worldnet.att.net> Reply-To: jkern3@visteon.com NNTP-Posting-Host: 19.53.49.17 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.75 [en]C-c32f404p (WinNT; U) X-Accept-Language: en, en-GB, de, fr, ja, ko, zh Xref: supernews.google.com comp.lang.ada:1683 Date: 2000-11-01T09:38:50-05:00 List-Id: James Rogers wrote: > > "E. Robert Tisdale" wrote: > > [[snip]] > This is also nonesense. It is easier to find C and C++ programmers > than Ada programmers. It is definitely NOT easier to train C and > C++ programmers than Ada programmers. > > Among other things, you must train C and C++ programmers to avoid the > numerous dangerous features of the language, particularly when > developing > real-time system. You can spend less time teaching Ada, without multiple > class hours spent on avoiding dangerous language features. I find it somewhat amusing that in the automotive arena, there is a whole industry of products available to keep the typical C programmer from screwing up. Our software process recommends, among the typical things, 'Safer C' training from Les Hatton, MISRA C coding guidelines, static analysis tools like QA C, OSEK compliant RTOSes for standardized kernel access, and UML tools that help us draw pictures of what we would have already done with Ada packages anyway. Also, there are the individual compiler issues and training, and the misguided attempts to achieve reuse by adding copious precompiler directives, etc. Have you ever noticed that whenever you service your car at a dealership, there is almost always a 'silent' software Technical Bulletin (recall) that has to be done?