From -3744430878055329446 X-Google-Thread: f78e5,a10702d4a7db0a94 X-Google-Attributes: gidf78e5,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!news3.google.com!news.glorb.com!peer1.news.newnet.co.uk!194.159.246.34.MISMATCH!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!stump.algebra.com!devnull From: francis@robinton.demon.co.uk (Francis Glassborow) Newsgroups: comp.std.c++ Subject: Re: Why no size_t to ::operator delete? Date: Wed, 27 Dec 2006 18:11:29 GMT Organization: Southfield Microcomputer SS Lines: 30 Sender: mail2news@demon.net Approved: fjh@cs.mu.oz.au (Fergus Henderson , moderator of comp.std.c++) Message-ID: <50wRTfE9yjkFFw7U@robinton.demon.co.uk> References: <12omt8jit7rl379@corp.supernews.com> <4591d812$0$13749$426a34cc@news.free.fr> NNTP-Posting-Host: news.news.demon.net Mime-Version: 1.0 Content-Type: text/plain;charset=us-ascii;format=flowed X-Trace: news.demon.co.uk 1167243099 15408 158.152.254.254 (27 Dec 2006 18:11:39 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Wed, 27 Dec 2006 18:11:39 +0000 (UTC) X-Original-To: std-c++@mailman.ucar.edu X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-User-Agent: Turnpike/6.03-U () X-Virus-Scanned: amavisd-new at csse.unimelb.edu.au X-Received: (from fjh@localhost) by mulga.csse.unimelb.edu.au (8.13.8+Sun/8.13.8/Submit) id kBRIBT40027241; Thu, 28 Dec 2006 05:11:29 +1100 (EST) X-Path: comp-std-cpp-robomod!not-for-mail X-Delivered-To: std-c++@mailman.ucar.edu X-Authentication-Warning: mulga.csse.unimelb.edu.au: fjh set sender to devnull@stump.algebra.com using -f X-Newsgroups: comp.std.c++ Xref: g2news2.google.com comp.std.c++:5179 In article <4591d812$0$13749$426a34cc@news.free.fr>, Mathias Gaunard writes >Andrew Koenig wrote: > >> Many moons ago I tried to convince the C++ community that there would >>be much to gain from abandoning malloc/free, but I could never find >>anyone willing even to consider it seriously. > >That's too bad. >malloc/free is seriously hurting C++. It must be the time of the year because I am finding it very difficult to understand how something I never use in C++ can be hurting C++. Could one of you try to explain. As far as I am concerned malloc/free is just there for compatibility with C (as is, for example, the printf and scanf families of functions) -- Francis Glassborow ACCU Author of 'You Can Do It!' and "You Can Program in C++" see http://www.spellen.org/youcandoit For project ideas and contributions: http://www.spellen.org/youcandoit/projects --- [ 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.comeaucomputing.com/csc/faq.html ]