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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,703c4f68db81387d X-Google-Thread: 109fba,703c4f68db81387d X-Google-Thread: 115aec,703c4f68db81387d X-Google-Thread: f43e6,703c4f68db81387d X-Google-Attributes: gid103376,gid109fba,gid115aec,gidf43e6,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!news.glorb.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!12.120.4.37!attcg2!ip.att.net!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada,comp.lang.c++,comp.realtime,comp.software-eng Subject: Re: [OT] Re: Teaching new tricks to an old dog (C++ -->Ada) Date: 10 Mar 2005 07:24:45 -0600 Organization: LJK Software Message-ID: References: <4229bad9$0$1019$afc38c87@news.optusnet.com.au> <1110032222.447846.167060@g14g2000cwa.googlegroups.com> <871xau9nlh.fsf@insalien.org> <3SjWd.103128$Vf.3969241@news000.worldonline.dk> <87r7iu85lf.fsf@insalien.org> <1110052142.832650@athnrd02> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1110461018 22683 192.135.80.34 (10 Mar 2005 13:23:38 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Thu, 10 Mar 2005 13:23:38 +0000 (UTC) Xref: g2news1.google.com comp.lang.ada:9034 comp.lang.c++:44958 comp.realtime:1199 comp.software-eng:4762 Date: 2005-03-10T07:24:45-06:00 List-Id: In article , azdo_b@yahoo.es (Alberto) writes: >> > >> > It looks like the code was not ISO C++ compliant. >> >> In that case, it looks like the compiler failed to detect that shortcoming. > > Well, it's time for me to join the 'American Dentist Association vs > C++' flame war: > > 1. Is Ada case-insensitive as Pascal? In that case, Ada==ADA Nobody objects to someone using the name ADA in a program written in Ada. The comments are about someone using improper capitalization in text written in English, a language which is case-sensitive. > 3. Many of you want us to believe that ADa performs ra nge checking > without loss of performance: it can be true at compile time with fixed > ranges, but it can't definitely be done without chechinkg array bounds > every time data is accessed if we don't know these bounds before > compiling (e.g.: typical cases where dynamic allocation of memory is > used) As has been stated, it is _much_ more efficient that do-it-yourself range checking written in C++, because the compiler has more data. For those who insist on _no_ range checking (compute intensive inner loops), turn off the range checking if it gets in the way for that one area of code. But be certain it gets in the way first - it is common to make bad guesses about whether range checking will affect overall performance. Ada programmers are better able than C* programmers to know that, because in Ada it is easier to turn range checking on and off. > mechanisms, only interfaces (pure virtual classes)[2]. To me, it > sounds reasonable to work with the last version of a compiler when > possible. That does not seem so reasonable to people working on a mission-critical 30 year project. In many cases such circumstances warrant working with the compiler originally used for the project.