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.4 required=5.0 tests=BAYES_00,FAKE_REPLY_C, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e6a2e4a4c0d7d8a6 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-02-20 14:59:14 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!fr.usenet-edu.net!usenet-edu.net!enst.fr!not-for-mail From: "David C. Hoos, Sr." Newsgroups: comp.lang.ada Subject: Re: status of PL/I as a viable language Date: Thu, 20 Feb 2003 17:00:48 -0600 Organization: ENST, France Message-ID: Reply-To: "comp.lang.ada mail to news gateway" NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 1045781953 12409 137.194.161.2 (20 Feb 2003 22:59:13 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Thu, 20 Feb 2003 22:59:13 +0000 (UTC) To: "comp.lang.ada mail to news gateway" Return-Path: X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.1 Precedence: list List-Id: comp.lang.ada mail to news gateway List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:34317 Date: 2003-02-20T17:00:48-06:00 ----- Original Message ----- From: "Peter Flass" Newsgroups: comp.lang.pl1,comp.lang.ada To: Sent: February 20, 2003 4:06 PM Subject: Re: status of PL/I as a viable language > "John R. Strohm" wrote: > > The last bug I found and fixed at my last employer was a null pointer > > access. That company has an internal coding policy that pointers will > > ALWAYS be tested for null before being dereferenced. > > I would submit that this should be done by hardware, not software (i.e. > location 0, assuming null is 0) should be fetch-protected from > everywhere but a few O/S routines. Anything else is a colossal waste of > computing resources. Well, that's probably what happened in this case. This would cause a segmentation fault, which would probably require more computing resource to recover from, as it would to test the pointer for null and take the appropriate action -- i.e., handling a signal costs more than testing the value of a register for zero/non-zero. > _______________________________________________ > comp.lang.ada mailing list > comp.lang.ada@ada.eu.org > http://ada.eu.org/mailman/listinfo/comp.lang.ada > >