From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10302020214.AA20883@clio.rice.edu>
Subject: Re: Time for a 2.04 alpha release on Simtel.NET?
To: djgpp-workers AT delorie DOT com
Date: Sat, 1 Feb 2003 20:14:00 -0600 (CST)
In-Reply-To: <3E3C5B9A.86C6E121@phekda.freeserve.co.uk> from "Richard Dawe" at Feb 01, 2003 11:43:22 PM
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

> > The updated dxegen/dxeload will potentially effect everything without
> > an FPU.
> 
> How close to completion is that? 

Iterating to completion.  DXE3 has been modified to be backward compatible,
DXE1 has been extended to support new things.  It's not all there yet - it
needs around 8 hours of time to finish out.

> Could it be pushed into 2.05? 

Really no - it needs to be the new foundation in the new libc so each
distribution gets it.

> I know the DXE upgrades are important, to stop iconv bloating all the 
> executables. Perhaps we could push that out into the betas?

Maybe, but it's risky for FPU emulator users.

> > There is also the unfinished business with malloc() ...
> 
> Has anything happened with regard to its memory debugging interface? I.e.: is
> it a slot-in replacement for the current malloc() yet?

Nothing yet

> Should we now consider malloc() to be 2.05 material?

Well, if we do that, then someone needs to fix the current libc free() to
early out if there are lots of items in the free list.

> 2.04 already has some big changes. If we wait any longer, I suspect it may not
> come out this year!

I believe alphas should be substationally feature complete.  Is C99 done
(or as done as we plan?)