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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 108717,ef0074ec236ba6e3 X-Google-Attributes: gid108717,public X-Google-Thread: 1014db,ef0074ec236ba6e3 X-Google-Attributes: gid1014db,public X-Google-Thread: 103376,b19fa62fdce575f9 X-Google-Attributes: gid103376,public X-Google-Thread: 109fba,ef0074ec236ba6e3 X-Google-Attributes: gid109fba,public X-Google-Thread: 1108a1,ef0074ec236ba6e3 X-Google-Attributes: gid1108a1,public X-Google-ArrivalTime: 1994-12-07 15:50:49 PST Path: bga.com!news.sprintlink.net!pipex!warwick!not-for-mail From: csusb@csv.warwick.ac.uk (Jules) Newsgroups: comp.lang.ada,comp.lang.c,comp.programming,comp.lang.c++,comp.object Subject: Re: Why don't large companies use Ada? Date: 7 Dec 1994 20:02:30 -0000 Organization: University of Warwick, Coventry, UK Message-ID: <3c54cm$il2@borage.csv.warwick.ac.uk> References: <3aa7jo$7j@Starbase.NeoSoft.COM> <1994Nov29.154220.27952@cognos.com> <3bimkh$149q@watnews1.watson.ibm.com> NNTP-Posting-Host: borage.csv.warwick.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Xref: bga.com comp.lang.ada:8380 comp.lang.c:33757 comp.programming:5687 comp.lang.c++:40037 comp.object:9564 Date: 1994-12-07T20:02:30+00:00 List-Id: In article , stef@heron.cfmu.eurocontrol.be (Stef Van Vlierberghe) writes: >In article <3bimkh$149q@watnews1.watson.ibm.com> ncohen@watson.ibm.com (Norman H. Cohen) writes: >- Classical C(++)-errors that aren't trapped at compile or run time > simply have no Ada equivalent. Just a few that I'm familiar with : > > if (a=0) oops_meant_equality; > > while (b /= a) oops_meant_inequality; Many compilers actually issue warnings in these cases, they are quite easy to trap. Admittedly, the warnings can get irritating if you want to do an assignment during an if statement. > > switch (a) > { case 1: one; > case 2: oops_forgot_the_break; Again, warnings can be quite easily produced in this situation. > (I have the impression that the rate at which I get bitten by these > doesn't decline over the years, mostly because I'm getting spoiled by > Ada between occasional C usage, but still I think this is an issue). I must admit, these are very frequent errors for many C programmers (myself included), especially once one has been using another language for a little while. Other frequent errors are caused by C's unusual syntax. Things that are hard to remember (such as the order of the arguments passed to main() - I always get them the wrong way around first time when I'm starting a new project) often just cause plain and simple irritation. -- /* Julian R Hall csusb@csv.warwick.ac.uk Flames should be redirected to /dev/null - I don't know what I'm saying myself so don't expect it to make sense all the time! */