From -3167520764533386935 X-Google-Thread: f78e5,a10702d4a7db0a94 X-Google-Attributes: gidf78e5,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!news3.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!pd7cy1no!shaw.ca!news.alt.net!comp-std-cpp-robomod!not-for-mail From: Mathias Gaunard Newsgroups: comp.std.c++ Subject: Re: Why no size_t to ::operator delete? Date: Tue, 26 Dec 2006 22:37:25 CST Organization: Guest of ProXad - France Lines: 19 Approved: Fergus Henderson , moderator of comp.std.c++ Message-ID: <4591d812$0$13749$426a34cc@news.free.fr> References: <12omt8jit7rl379@corp.supernews.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: 1167185939 news-4.free.fr 13749 82.233.64.48:52743 X-Complaints-To: abuse@proxad.net NNTP-Posting-Date: 27 Dec 2006 03:18:59 MET Return-Path: X-Authentication-Warning: mulga.csse.unimelb.edu.au: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Original-To: std-c++@mailman.ucar.edu Delivered-To: std-c++@mailman.ucar.edu User-Agent: Thunderbird 1.5.0.8 (X11/20061115) X-Virus-Scanned: amavisd-new at ucar.edu X-Virus-Scanned: amavisd-new at csse.unimelb.edu.au X-Virus-Scanned: amavisd-new at csse.unimelb.edu.au Xref: g2news2.google.com comp.std.c++:5177 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++. We could also introduce a standard LIFO allocator, which just works in most cases (when you don't need to transcend scope) and is way more efficient. --- [ 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 ]