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: 107f24,582dff0b3f065a52 X-Google-Attributes: gid107f24,public X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,582dff0b3f065a52 X-Google-Attributes: gid1014db,public X-Google-Thread: 109fba,582dff0b3f065a52 X-Google-Attributes: gid109fba,public X-Google-ArrivalTime: 2001-08-06 07:40:00 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!newsgate.cistron.nl!news.worldonline.nl!newsclients!news.worldonline.nl!not-for-mail From: info@hoekstra-uitgeverij.nl (Richard Bos) Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.lang.functional Subject: Re: How Ada could have prevented the Red Code distributed denial of service attack. Date: Mon, 06 Aug 2001 13:51:55 GMT Organization: Go wash your mouth. Message-ID: <3b6e981c.1477345425@news.worldonline.nl> References: <9kci3p$ri$1@elf.eng.bsdi.com> <9kdeuv$dfh@augusta.math.psu.edu> <3b6a4414.1193645865@news.worldonline.nl> <9ked75$fa8@augusta.math.psu.edu> NNTP-Posting-Host: vp225-251.worldonline.nl X-Trace: nereid.worldonline.nl 997108515 25004 195.241.225.251 (6 Aug 2001 14:35:15 GMT) X-Complaints-To: newsmaster@worldonline.nl NNTP-Posting-Date: 6 Aug 2001 14:35:15 GMT X-Newsreader: Forte Free Agent 1.21/32.243 Xref: archiver1.google.com comp.lang.ada:11364 comp.lang.c:72450 comp.lang.c++:80308 comp.lang.functional:7336 Date: 2001-08-06T14:35:15+00:00 List-Id: cross@augusta.math.psu.edu (Dan Cross) wrote: > In article <3b6a4414.1193645865@news.worldonline.nl>, > Richard Bos wrote: > >Says who? When I write a bug, it's _my_ bug. > > I see. And have you ever worked on a project with more than one > programmer? Sure. And when I write a bug, it's still my bug. When one of us writes a bug but I don't know who did it yet, it's our bug. It's called "responsibility". And it's the programmer's responsibility, _not_ the tools'. > > > > > > Who ever said there was a language that would prevent one from making a > mistake? You patently do not understand the meaning of the word "sarcasm". You must be a USAlien. > >That's why I check and test my programs before using them for production > >work. With "modern" programmers, that's becoming an ever rarer > >procedure, alas. > > Indeed, today's programmer's attitude towards quality and quality > assurance represents a sad truly state of affairs. Case in point, > programmers who feel that their work is done in a bubble, and refuse to > use tools which are likely to reduce [*] instances of error injection. Such as? Let me remind you that array bounds checking only allows you to spot array bounds infringements _after_ they have happened. Only a thorough design can help prevent bugs to occur in the first place. Richard