X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Tue, 5 Mar 2002 07:44:57 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp-workers AT delorie DOT com
Subject: Re: Malloc/free DJGPP code
In-Reply-To: <3C840B4F.96B43316@yahoo.com>
Message-ID: <Pine.SUN.3.91.1020305074332.17597C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 4 Mar 2002, CBFalconer wrote:

> > The calls to such hooks could be via function pointers, only if they
> > are non-NULL.  If they are set to NULL by default, the overhead is
> > just a simple test.
> 
> It is not necessary IMO.  Any such can be done by inserting and
> calling custom routines, without worrying about interfering with
> initialization etc.

Features such as those in malldbg.c cannot be implemented that way, since 
they are meant to be used by ordinary users, not source code hackers.

For example, how do you implement a feature that shows a report of 
allocated and free blocks?