Just to rule out any possibility it is your sort routine, comment out your
code
and replace it with: "return 0;"
Now all the records should compare equal to each other and see if crashes in
this
case. If it does, then it definately sounds like it is not your fault.
btw, the standard textbook quicksort works by dividing the records in 2 and
recursively quicksorting each
part and then combining them again. It is indeed possible that adding those
extra
20 records has caused it to recurse one level deeper and thus run out of
memory. I dunno how the Palm QuickSort function is implemented though.
Brandon
----- Original Message -----
From: Steve <[EMAIL PROTECTED]>
To: Palm Developer Forum <[EMAIL PROTECTED]>
Sent: Tuesday, April 04, 2000 11:04 AM
Subject: Re: Database Sorting Problem
> >So I therefore
> >conclude that there is something in DmQuickSort which can't handle a sort
> >larger than 16384.
>
> FWIW I've just verified the same behavior is observed in OS 3.5, so
> whatever problem exists has not been recently fixed.
>
> Steve Patt
> President, Stevens Creek Software
> http://www.stevenscreek.com/palm
> Best PQA ("ePQA"), PalmSource 99
> Best Application ("PizzaScan"), Palm Developer's Conference 1998
> First printing software for the Palm - September, 1997
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
