Mail Archives: djgpp-workers/2003/04/20/23:52:21
> Date: Sun, 20 Apr 2003 18:56:08 -0400
> From: CBFalconer <cbfalconer AT yahoo DOT com>
>
> > > To address Charles Sandmanns concern over the documentation, I
> > > have implemented it exactly to the existing documentation, with
> > > the exception that malloc_debug has an additional FILE* parameter
> > > to set the file on which to display results. If that is NULL
> > > stderr is used. Easily changed back to eliminate the FILE*, and
> > > add a new name or macro for that functionality.
> >
> > That's okay, but the additional functionality--the ability to control
> > where the messages go--needs to be documented.
>
> I agree, but the mechanics of it are not simple for me. The doc
> change is only a line or two in the description of malloc_debug.
Simply modify malloc.txh--it's almost a plain text file. If you are
unsure about the markup, just do what you think is right, and someone
else will fix it if required.
> This is the end plan, more or less, NOT the way it acts in
> nmalloc.zip. But I see a plain path to it, PROVIDED everything is
> functional and tested with who knows what.
I don't have any objections, but this work needs to be done before
nmalloc is made part of the library.
- Raw text -