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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 101deb,3488d9e5d292649f X-Google-Attributes: gid101deb,public X-Google-Thread: 103376,e6a2e4a4c0d7d8a6 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-02-20 14:06:50 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!cyclone.swbell.net!newsfeed1.easynews.com!easynews.com!easynews!news-west.rr.com!cyclone.nyroc.rr.com!cyclone-out.nyroc.rr.com!twister.nyroc.rr.com.POSTED!not-for-mail Message-ID: <3E554AF4.C8F0EF2E@yahoo.com> From: Peter Flass X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.pl1,comp.lang.ada Subject: Re: status of PL/I as a viable language References: <3E51908E.9CCA3412@adaworks.com> <8Gh4a.7455$_c6.743959@newsread2.prod.itd.earthlink.net> <3E51ABCE.5491B9A2@adaworks.com> <3E5273DE.2050206@cox.net> <3E531E6F.BDFB2599@adaworks.com> <3E546C45.4010406@cox.net> <3E54F926.441D5BB5@adaworks.com> <1045763933.848350@master.nyc.kbcfp.com> <42EA55F4BE83950E.F1DA277C2FDC157B.C804C1C52FE95D65@lp.airnews.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 Feb 2003 22:06:47 GMT NNTP-Posting-Host: 24.194.50.82 X-Complaints-To: abuse@rr.com X-Trace: twister.nyroc.rr.com 1045778807 24.194.50.82 (Thu, 20 Feb 2003 17:06:47 EST) NNTP-Posting-Date: Thu, 20 Feb 2003 17:06:47 EST Organization: Road Runner Xref: archiver1.google.com comp.lang.pl1:4374 comp.lang.ada:34313 Date: 2003-02-20T22:06:47+00:00 List-Id: "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.