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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,78b2880bc7e78e39 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-03-20 14:32:07 PST Newsgroups: comp.lang.ada Path: supernews.google.com!sn-xit-03!supernews.com!freenix!skynet.be!newspump.sol.net!nntp.msen.com!uunet!ash.uu.net!world!bobduff From: Robert A Duff Subject: Re: RISC Sender: bobduff@world.std.com (Robert A Duff) Message-ID: Date: Tue, 20 Mar 2001 22:30:06 GMT References: <98qumf$5sf$1@nh.pace.co.uk> <98r4g1$7r1$1@nh.pace.co.uk> <3ab1d090$1@pull.gecm.com> <98t8la$rc$1@nh.pace.co.uk> <3ab72c8f$1@pull.gecm.com> <997pq4$i35$1@nh.pace.co.uk> <3ab79ade$1@pull.gecm.com> <998ctp$ond$1@nh.pace.co.uk> Organization: The World Public Access UNIX, Brookline, MA X-Newsreader: Gnus v5.3/Emacs 19.34 Xref: supernews.google.com comp.lang.ada:5937 Date: 2001-03-20T22:30:06+00:00 List-Id: "Marin David Condic" writes: > Sounds to me like it says: "If you use an address clause to achieve an > overlay you are being a very bad, bad, programmer and should be made to stay > after programming school and write on the blackboard 'Thou Shalt Not > Overlay' 1000 times and learn that the compiler cannot save you if you do > stupid things like this. But if nobody is looking and the compiler doesn't > complain and it works anyway, the LRM won't have anything against this..." Erroneous means that, but it also means that your program can do absolutely anything, including wipe out your disk or (much worse) work properly until you port it or turn on the optimizer or upgrade your compiler. The "erroneous" rule about overlays was removed from Ada 95 quite deliberately, because it was recognized that there are (rare) circumstances where it makes sense to use overlays. And because we weren't entirely sure what "overlay" means in a formal sense. Most of the remaining rules about "erroneous" are there for good reason: eg, an optimizing compiler really might do something very surprising, causing subtle bugs that occur only rarely. And note that rare bugs are the ones that matter. A bug that occurs the first time you run the program will be found right away, and fixed. A rare bug might escape to customers. - Bob