Message-ID: <35A3B749.50BC@teleline.es>
Date: Wed, 08 Jul 1998 20:15:37 +0200
From: Mariano Alvarez Fernández <malfer AT teleline DOT es>
Reply-To: malfer AT teleline DOT es
Organization: teleline.es
MIME-Version: 1.0
To: Nate Eldredge <nate AT cartsys DOT com>
CC: djgpp AT delorie DOT com, eliz AT is DOT elta DOT co DOT il
Subject: Re: About DJGPP v2.02
References: <35A2AA9E DOT 7CE4 AT teleline DOT es> <35A2F203 DOT 8687D81D AT cartsys DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Nate Eldredge wrote:

> >
> > Yes, it crashed (v2.02 980101) under Windows, I didn't try it. Oops!
> > I will try the latest alpha.
> 
> It's not recommended to use for production code, but there's nothing 
> to stop you from doing so.  Use it at your own risk!

No, I will not release my program with the alpha library, I'm only
testing it because I want to use DJGPP.

> >
> > Yes, I profiled it and all the time is wasted whit __dpmi_int, as
> >the 13.5 in the FAQ says.
> 
> If you get a profiling libc (2.01 with bugs fixed) from
> 
> http://www.cartsys.com/eldredge/djgpp-patches.html
> 
> you will be able to tell what is calling `__dpmi_int' for so much 
> time.

Thanks, I will test it.

> 
> Do you read a lot from a file, or seek a lot?  2.02 uses a different
> algorithm which may speed that up, but I wouldn't expect it to be that
> drastic.
> 

Eli Zaretskii wrote:
> One thing that v2.02 changes is the way buffered file I/O works.
> v2.02 adapts itself better to the specific use of buffered I/O
> functions (sequential vs. random access), which should show in
> programs that seek into files a lot.  Perhaps your program is one of
> those?

Yes I seek a lot, the data-bases are shared in a LAN, I can't pre-read
because any body can update it, I use lock files as semaphores.
Obviously the new algorithm works great for me :-)

Thanks DJ, Nate, Eli, SET, Robert, ... for DJGPP, it's a wonderful work.

Regards, M.Alvarez