On Sat, 19 Aug 2000, Yukihiro Matsumoto wrote:

> Hi,
> 
> In message "[ruby-talk:04502] methods w/ ! giving nil"
>     on 00/08/18, Hugh Sasse Staff Elec Eng <hgs / dmu.ac.uk> writes:
> |
> |I have got used to the idea that methods that end in '!' return nil if
> |nothing changes.  But not all of them do.  Why does array.sort! not behave
> |like that?  Why should it be different from the array.uniq! method in this
> |respect?
> 
> Mostly because underlying qsort(3) does not provide the way to know if
> modification is happened.  I will gladly accept any idea to implement
> consistent ! behavior without performance penalty.

That makes sense.  Could Ruby have its own qsort routine (in C) that
achieves this notification?
> 
> 							matz.
	Hugh
	hgs / dmu.ac.uk