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: 103376,1ff5003422436e4 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-10-25 18:43:10 PST Path: nntp.gmd.de!newsserver.jvnc.net!netnews.summit.novell.com!netnews.summit.novell.com!not-for-mail From: jls@summit.novell.com (-mlc-+Schilling J.) Newsgroups: comp.lang.ada Subject: Re: Easily-Read C++? Date: 25 Oct 1994 20:39:30 -0400 Organization: Novell, Summit Message-ID: <38k8g2INNiff@marble.summit.novell.com> References: <389vqv$i6n@source.asset.com> NNTP-Posting-Host: marble.summit.novell.com Date: 1994-10-25T20:39:30-04:00 List-Id: In article <389vqv$i6n@source.asset.com> bishopm@source.asset.com (Michael M. Bishop) writes: >In article , Thomas M. Breuel wrote: >>On the other hand, real-world users will probably >>not accept a language that doesn't provide some equivalent of C's >>plain arrays: the overhead of carrying bounds information around at >>runtime is sometimes unacceptable. > >You don't have to carry Ada array bounds information around at run-time. >You can use the pragma Suppress to remove those checks from the >generated object code. Pragma Suppress doesn't relate to carrying around array bounds at runtime, but rather to whether index checks are done. If the array bounds are dynamic, then it is necessary to carry them around in order to generate correct indexing offset code, whether or not you are also doing the checks. But more to the original point, if Ada arrays are declared as equivalents of C's plain arrays, then the bounds will be static and they will _not_ be carried around at runtime. (The bounds will materialise if you pass the array to an unconstrained formal, but this happens to some extent in C as well - typically you pass in both the beginning and ending addresses of an array.) -- Jonathan Schilling Novell, UNIX Systems Group jls@summit.novell.com