«

Peter Duniho wrote:

> But, absent a specific, useful question I would say that the most likely
> cause of the behavior you're describing would be an incorrect comparison
> implementation, one that returns non-deterministic results.


Well, if we're going to speculate, I see two potential likely issues:

1. OP was unaware of objects with some default values in the array and
incorrectly assumed they were added during the sort.

2. Some other part of the program is changing values and the OP is again
assuming incorrectly that it was the sort that made the changes.

Peter Duniho wrote:

> Oh sure, modify the problem statement by presuming (however confidently
> ) that the OP has mis-stated the actual conditions of the problem.


Yeah, that never happens here. I'm really out on a limb, aren't I?