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!postnews.google.com!g14g2000cwa.googlegroups.com!not-for-mail From: "Jerry Coffin" Newsgroups: comp.lang.ada,comp.lang.c++,comp.realtime,comp.software-eng Subject: Re: Teaching new tricks to an old dog (C++ -->Ada) Date: 9 Mar 2005 14:53:24 -0800 Organization: http://groups.google.com Message-ID: <1110408804.335616.161030@g14g2000cwa.googlegroups.com> 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> <87is4598pm.fsf@insalien.org> <1110054476.533590@athnrd02> <1110059861.560004@athnrd02> <87wtsl7jts.fsf@insalien.org> <1110264816.858853.54020@l41g2000cwc.googlegroups.com> <1110336185.044049.21920@l41g2000cwc.googlegroups.com> <87wtsgfo7l.fsf@insalien.org> NNTP-Posting-Host: 165.236.235.120 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1110408808 31851 127.0.0.1 (9 Mar 2005 22:53:28 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 9 Mar 2005 22:53:28 +0000 (UTC) User-Agent: G2/0.2 Complaints-To: groups-abuse@google.com Injection-Info: g14g2000cwa.googlegroups.com; posting-host=165.236.235.120; posting-account=mZiOqwwAAAC5YZsJDHJLeReHGPXV5ENp Xref: g2news1.google.com comp.lang.ada:8983 comp.lang.c++:44867 comp.realtime:1159 comp.software-eng:4717 Date: 2005-03-09T14:53:24-08:00 List-Id: Ludovic Brenta wrote: [ ... ] > No, I did insist on aliasing as the main point, and then briefly > about the representation clause that caused two objects to be > overlaid. Well, I just went back and reread your post, and I still don't see it, but if you think that's what you said, so be it. > Aliasing is definitely *not* orthogonal to safety. The coding > standards I have reviewed for avionics, as well as the "Guide for the > use of the Ada programming language in High Integrity Systems" [1] > all discuss how aliasing adversely affects safety. It is important, > in safty-critical software, to understand aliasing: what it is, when > it takes place, and what the consequences are. Performance in this > context is a minor concern compared to predictability of the > software. > > [1] http://www.dkuug.dk/JTC1/SC22/WG9/n359.pdf I read through the reference above, and what it says about aliasing is basically "We've built a program verification system that doesn't understand aliasing, so attempting to use our system on code that uses aliasing won't work." Perhaps you intended to post some other link? -- Later, Jerry. The universe is a figment of its own imagination.