From: Joern Rennecke <amylaar@cygnus.co.uk>
To: ncm@cygnus.com (Nathan Myers)
Cc: egcs@cygnus.com
Subject: Re: malloc/free & new/delete balance
Date: Mon, 06 Jul 1998 14:48:00 -0000 [thread overview]
Message-ID: <199807062124.WAA12419@phal.cygnus.co.uk> (raw)
In-Reply-To: <35A01664.383F9BDB@cygnus.com>
> *You* try to write a requirement that the storage is re-used without
> actually specifying an algorithm. The C committee gave up, and the
> C++ committee doesn't claim to be (much :) smarter.
How about listing some minimum requirement, like:
if an object is freed, and the next allocation is for an object of the
same size, that allocation will succeed.
next prev parent reply other threads:[~1998-07-06 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199807031202.IAA26419.cygnus.egcs@maniac.deathstar.org>
1998-07-05 19:46 ` Nathan Myers
1998-07-06 14:48 ` Joern Rennecke [this message]
1998-07-06 18:52 ` John Carr
1998-07-07 1:12 ` Joern Rennecke
1998-07-03 7:20 Sol Foster
1998-07-03 19:30 ` Carlo Wood
-- strict thread matches above, loose matches on Subject: below --
1998-07-01 22:54 Mike Stump
1998-07-02 1:39 ` Alexandre Oliva
1998-06-30 14:46 Sol Foster
1998-06-29 8:41 Carlo Wood
1998-06-30 1:02 ` Alexandre Oliva
1998-06-30 15:15 ` Carlo Wood
1998-06-30 14:46 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199807062124.WAA12419@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=ncm@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).