Message-ID: <38887509.59DA02E2@cyberoptics.com>
From: Eric Rudd <rudd AT cyberoptics DOT com>
Organization: CyberOptics
X-Mailer: Mozilla 4.08 [en] (Win95; U)
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: qsort() bug?  Or invalid usage???
References: <R0Gh4.2371$Ll5 DOT 3502 AT news2 DOT randori DOT com> <867gpd$k0u$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <388758A7 DOT 1B64BDF9 AT cyberoptics DOT com> <388824A4 DOT 7E8CA268 AT is DOT elta DOT co DOT il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 17
Date: Fri, 21 Jan 2000 09:02:34 -0600
NNTP-Posting-Host: 38.196.93.9
X-Trace: client 948466955 38.196.93.9 (Fri, 21 Jan 2000 10:02:35 EST)
NNTP-Posting-Date: Fri, 21 Jan 2000 10:02:35 EST
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:

> Eric Rudd wrote:
> >
> > Yes, and equal objects must return 0.  The last time I checked, DJGPP's qsort
> > implementation sometimes attempts to dereference beyond the ends of the array
> > if the comparison function returns inconsistent results.
>
> When was that ``last time''?  The implementation of `gsort' in the DJGPP
> library was changed between v2.01 and v2.02.

I see that indeed it has.  At the time I was having problems, DJGPP used the BSD
qsort algorithm.  I am glad to see that K. B. Williams has provided new code, so
there's hope that the problem has been solved.  I will run a few tests on it to see
how it performs.