From -4805870483887435758 X-Google-Language: ENGLISH,ASCII X-Google-Thread: f78e5,176c9dc06a6729eb X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2002-03-28 09:48:04 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!dispose.news.demon.net!news.demon.co.uk!demon!mail2news.demon.co.uk!not-for-mail From: "Michel de Becdeli�vre" Newsgroups: comp.std.c++ Subject: Re: why doesn't delete NULL the pointer? Date: Thu, 28 Mar 2002 17:47:02 GMT Organization: Guest of France Telecom Oleane's newsreading service Approved: Fergus Henderson , moderator of comp.std.c++ Message-ID: References: <3C9DD892.94860335@acm.org> <3C9F938C.5060805@animats.com> X-Trace: mail2news.demon.co.uk 1017337627 mail2news:29599 mail2news mail2news.demon.co.uk X-Complaints-To: abuse@demon.net X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) NNTP-Posting-Date: Thu, 28 Mar 2002 09:23:10 +0000 (UTC) X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Lines: 29 Xref: archiver1.google.com comp.std.c++:10273 There are tools to catch this kind of error (such as Purify available both on UNIX and WinNT), and in my experience they pay for themselves in less than a week on any project needing more than a single programmer. Unless you are working on cross platforms or tight real time, you should try to convince your management to buy one of those (I only have experience with Purify, but there are other solutions on the market, and the best of those tools also track file handle leakage, and other hard to find errors like this - memory is only the most commonly misused ressource used in a program). "Scott Robert Ladd" a �crit dans le message de news: BZoo8.4> many > Very true; an excellent programmer with professional skills will not make > memory management errors. However, I've just spent two days digging out > memory allocation errors in code written by someone with 15 years of "C++ > experience". In my experience, there just aren't that many "professional" > programmers -- and that's why we have dumbed-down versions of C++ called > Java and C# (neither of which, BTW, are immune to memory corruption > problems). --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.research.att.com/~austern/csc/faq.html ]