From: Simon Wright <simon@pushface.org>
Subject: Re: Deallocating an object twice
Date: Mon, 28 Jul 2014 17:15:35 +0100
Date: 2014-07-28T17:15:35+01:00 [thread overview]
Message-ID: <lylhrdqx20.fsf@pushface.org> (raw)
In-Reply-To: 8538dlqzu8.fsf@stephe-leake.org
Stephen Leake <stephen_leake@stephe-leake.org> writes:
> Don't copy pointers! It is the copy of the pointer that is bad, not
> the behavior of Unchecked_Deallocation.
I don't think pointers are always bad, so long as everyone knows whose
responsibility it is to do the allocation and deallocation.
prev parent reply other threads:[~2014-07-28 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 19:55 Deallocating an object twice Victor Porton
2014-07-26 20:02 ` Victor Porton
2014-07-27 2:39 ` Randy Brukardt
2014-07-27 2:42 ` Randy Brukardt
2014-07-27 8:31 ` Simon Wright
2014-07-27 11:30 ` anon
2014-07-27 12:47 ` Peter Chapin
2014-07-27 15:29 ` Stephen Leake
2014-07-27 15:34 ` Victor Porton
2014-07-28 15:15 ` Stephen Leake
2014-07-28 16:15 ` Simon Wright [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox