X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Date:	Sat, 30 May 2015 17:06:56 +0200
From:	Damien <damien DOT guibouret AT partition-saving DOT com>
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050416
X-Accept-Language:	en-us, en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP v2.05: some thoughts
References:	<55673F0B DOT 1090103 AT iki DOT fi>
In-Reply-To:	<55673F0B.1090103@iki.fi>
Lines:	69
Message-ID:	<5569d1c7$0$3304$426a34cc@news.free.fr>
Organization:	Guest of ProXad - France
NNTP-Posting-Date:	30 May 2015 17:05:43 CEST
NNTP-Posting-Host:	82.230.26.21
X-Trace:	1432998343 news-4.free.fr 3304 82.230.26.21:40032
X-Complaints-To:	abuse AT proxad DOT net
Bytes:	3632
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Andris Pavenis (andris DOT pavenis AT iki DOT fi) wrote:
> I think it would be best to get DJGPP v2.05 actual release out soon 
> enough. It would not be nice to repeat what happened with v2.04 again.
> 
> Some questions that should be answered for that:
> - what critical problems we have what should be fixed for release
> - what we want in and what can wait
> 
> Making release would include also moving out current stuff from 
> pub/djgpp/current (one should be careful with source packages) and 
> moving files from pub/djgpp/beta to current (possibly not all) and other 
> related changes.
> 
> There is danger of repeating history with v2.04 if begin to add too much 
> new stuff or new changes.
> 
> One possible new feature that comes into mind :
> - changes for more full support of wide characters have been around for 
> a long time. We must decide whether we want to get it in v2.05 or we 
> should wait after release.
> 
> One of critical problems which as I think should be fixed if possible:
> - problems with DXE built with gcc-5.1.0 (I only tested 4.7.3 which is 
> OK and 5.1.0).
> 
> There could be additional issues of course.
> 
> CVS branch for release should perhaps be created after getting possible 
> new features in. This way it would be possible to continue development 
> and avoid destabilizing 2.05 so release could be done in reasonable time.
> 
> Andris
> 

Hello,

I did some test with this version 2.05 and did not get any problem using it. The 
change in memory deallocation time is impressive (less than 1s for a bunch of 
deallocations when it tooks 5s with version 2.04).

Some time ago, I had signaled a trouble with XP NTVDM. The bug is in XP, not in 
DJGPP, and is still present with Seven, but it could easily be workarounded in 
DJGPP. You can get the explanation and associated patch in 
http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2005/11/21/15:28:15
The program that allows showing this is the following:
#include <stdio.h>
#include <string.h>
#include <dir.h>

int main(void) {
   struct ffblk desc;
   int status;

   strcpy(desc.lfn_magic, "LFN32");
   status = findfirst("*", &desc, FA_RDONLY | FA_HIDDEN | FA_SYSTEM | FA_LABEL | 
FA_DIREC | FA_ARCH);
   while (status == 0) {
     printf("%s\n", desc.ff_name);
     status = findnext(&desc);
   }

   return 0;
}
This program shall be executed in a directoy containing 2 files (one named 
a_long_filename, second one named €_euro_char) to show the problem.

Regards,

Damien

- Raw text -