🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.c++
Article #2079

Re: Why not op delete(void* v&,size_t);?

#2079
From: Ronald F. Guilmette
Date: Sat, 30 Sep 1995 19:04
26 lines
1496 bytes
In article <434me4$ov3@citadel.evolving.com>,
Todd Blanchard <tblancha@evolving.com> wrote:
>void operator delete(void*,size_t);
>...
>Nowhere can I find a rational explanation for why the pointer is not
>passed as a void*& (to allow zeroing).  It would provide more 
>flexibility in memory management schemes.

Maybe the answer is that delete came before references... then again,
maybe not.

Heck!  If you are going to ask about _that_ why not ask why member
functions get a `this' _pointer_ rather than a `this' reference?
The latter would clearly have been a far better choice.
-- 

-- Ron Guilmette, Roseville, CA -------- Infinite Monkeys & Co. ------------
---- E-mail: rfg@monkeys.com ----------- Purveyors of Compiler Test Suites -
----------------------------------------------------------------------------


---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
Technical Details
Message-ID: <44irni$10e@segfault.monkeys.com>
Path: arc1-ca.pugleaf.net!spool.mu.edu!agate!agate!Matt
References: <9509082051.AA01889@dawn.megaeng> <434me4$ov3@citadel.evolving.com>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!spool.mu.edu!agate!agate!Matt
From: rfg@monkeys.com (Ronald F. Guilmette)
Newsgroups: comp.std.c++
Subject: Re: Why not op delete(void* v&,size_t);?
Date: 30 Sep 1995 19:04:28 GMT
Organization: Infinite Monkeys & Co.
Approved: Matt@Austern
Message-ID: <44irni$10e@segfault.monkeys.com>
References: <9509082051.AA01889@dawn.megaeng> <434me4$ov3@citadel.evolving.com>
NNTP-Posting-Host: austern.hip.berkeley.edu