Date: Tue, 8 May 2001 10:35:06 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: djgpp-workers AT delorie DOT com
Subject: Re: DJGPP 2.04 release date
In-Reply-To: <3AF6DBD7.496DE8C6@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1010508103030.3965O-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, 7 May 2001, Richard Dawe wrote:

> Eli Zaretskii wrote:
> > For v2.04, I believe we don't even have a tentative release date
> > (perhaps we should, btw).
> 
> Don't we need a set of release criteria first?

It would be good to have that, but I thought that the list of features
we added already, whatever it is, is good enough to be those criteria ;-)

> I think we need:
> 
> * GCC 3.0 support => dependent on gcc 3.0 release;
> * Win2k support;

Don't worry about this: experience shows that the release cycle takes
several months, so, by the time we're done, these will probably be in
anyway, one way or the other.  OTOH, if GCC 3.0 isn't released in a
few months, it probably isn't worth waiting for.

> * solid testing of FAT32 & symlinks.

The symlinks won't be tested ``solidly'' until all the major ported
development tools are rebuilt with symlink support and people begin
using them.  Making such versions now could be a good idea.

As for FAT32, I think it is tested quite well; FWIW, I'm running Emacs
built with that support for quite some time.

> * snprintf(), vsnprintf();
> * /dev/zero, /dev/full (still waiting for paperwork from my employer -
> <sigh>).

snprintf is close to being finished, if only Someone (tm) addresses my
concerns about n == 0 etc.  /dev/full and /dev/zero would be good to 
have, but I don't see this as a must, in case you legal trouble isn't
solved.

> What else is there?

You want a shopping list? ;-)  Here it is:

  - core dump support
  - c99 compatible headers (stdbool.h, stdint.h, inttypes.h, etc.)
  - setlocale which really does something useful
  - more format specifiers for *printf (%1, %', etc.)
  - chroot (or is that already checked in?)
  - mkdoc changes (or did we already commit them?)
  - ``namespace std'' nuisance with standard C headers

Larger projects (probably better left for after v2.04):

  - c99 functions we don't have
  - utf-8 based support for wide characters
  - functions from the latest Posix draft (posix_spawn etc.)

In addition, I have a wish list of enhancements that are hard to
explain in one punch line; if someone wants to hear, I will post their
descriptions.