X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10205161713.AA12973@clio.rice.edu>
Subject: Re: Malloc/free DJGPP code
To: djgpp-workers AT delorie DOT com
Date: Thu, 16 May 2002 12:13:30 -0500 (CDT)
In-Reply-To: <3CE37BCA.F5DE2858@yahoo.com> from "CBFalconer" at May 16, 2002 05:28:42 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> Why does evaluation depend solely on you?  

It doesn't.  I just happen to believe it ought to get fixed, happen
to have lots of experience in this area.  If someone else runs with
it I'd be quite happy.

> Although both free and
> realloc have at least one serious problem each in the current
> distribution, nobody else seems to give the proverbial rat's a ss.

Serious problem is relative.  I rate problems by impact.  Anything
which is a performance issue (elapsed time or resources consumed)
but works is a lower priority than something which doesn't
work at all.

For things that don't work at all, I then prioritize by how 
frequently that happens, and if there is a workaround.

V2.03 didn't really work at all on the only Windows platform which will
provide DOS in the future (Win2K/XP).  That was a serious problem.
There are a few problems left, but they are now small problems.

GCC 3.1 won't work properly with V2.03 - that's a less serious problem
since there is a workaround to hand edit some include files, but it
still doesn't do the right thing.

The malloc() problems are performance only, and will be fixed in the
next release (longer time frame).