Date: Wed, 23 Oct 2002 07:49:42 +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: CBFalconer's malloc
In-Reply-To: <10210230425.AA17374@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1021023074655.13511B-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 Tue, 22 Oct 2002, Charles Sandmann wrote:

> > I am trying to make sure that this exchange contains a list of
> > things needed to be done, so I have unsnipped a portion.  Please
> > keep it a massive whole, so I can eventually use it for review.
> 
> No :-)

I concur.  Keeping all the exchange together for a long thread makes it 
very hard to read the messages quickly.

I usually coincatenate all the messages together to get a clear picture 
of the discussion.

> In addition, I don't think it has to be done exactly the way it's
> done today, as long as the functionality is the same and the 
> documentation is updated to reflect the way to do it, and 
> diagnostic helper routines/examples are provided.

Yes, I agree.

> The current CVS code has never been officially released, so unless
> someone points out someone using the interfaces as written, I think
> it's fair to discuss changes.

It's cetrtainly fair.  All I care about is that malldbg functionality be 
preserved, more or less.

> There is no on-line help or detailed examples such as malldbg has;
> so the how to is less clear.

I think malldbg is an example in itself.