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,e6a2e4a4c0d7d8a6
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-24 04:00:13 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.ems.psu.edu!news.litech.org!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!out.nntp.be!propagator-sanjose!news-in-sanjose!newsfeed.onecall.net!chcgil2-snf1.gtei.net!news.gtei.net!news.binc.net!kilgallen
From: Kilgallen@SpamCop.net (Larry Kilgallen)
Newsgroups: comp.lang.ada
Subject: Re: status of PL/I as a viable language
Date: 24 Feb 2003 06:00:06 -0600
Organization: Berbee Information Networks Corporation
Message-ID: <kHz6GI3rfZS+@eisner.encompasserve.org>
References: <mHZ0a.42983$jM5.108891@newsfeeds.bigpond.com>
 <nRg1a.190899$HG.32437469@news4.srv.hcvlny.cv.net>
 <3E51908E.9CCA3412@adaworks.com>
 <8Gh4a.7455$_c6.743959@newsread2.prod.itd.earthlink.net>
 <3E51ABCE.5491B9A2@adaworks.com> <b2spe6$p23$1@helle.btinternet.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>
 <1045769690.1Organization: LJK Software
NNTP-Posting-Host: eisner.encompasserve.org
X-Trace: grandcanyon.binc.net 1046087990 22979 192.135.80.34 (24 Feb 2003
 11:59:50 GMT)
X-Complaints-To: abuse@binc.net
NNTP-Posting-Date: Mon, 24 Feb 2003 11:59:50 +0000 (UTC)
Xref: archiver1.google.com comp.lang.ada:34505
Date: 2003-02-24T06:00:06-06:00
List-Id: <comp.lang.ada>

In article <UPi6a.4466$8f7.333@nwrdny02.gnilink.net>, Hyman Rosen <hyrosen@mail.com> writes:

> As for my credit card safety, have you seen the news lately? About
> the easy attacks on ATM PIN numbers that can have bank insiders
> steal your money in fifteen tries or less? Complex software has
> complex failure modes. Patting yourself on the back for catching
> buffer overruns is a little premature.

Patting oneself on the back for always avoiding automated tools for
catching buffer overflows is also silly, and some C* programmers do
that.  (Yes, I group C, C++, C# all together, because many of their
advocates do, praising the ability to write C with a C++ compiler.)