[#4567] Re: What's the biggest Ruby development? — Aleksi Niemel<aleksi.niemela@...>

Dave said:

18 messages 2000/08/23
[#4568] Q's on Marshal — Robert Feldt <feldt@...> 2000/08/23

[#4580] RubyUnit testcase run for different init params? — Robert Feldt <feldt@...> 2000/08/25

[#4584] Re: RubyUnit testcase run for different init params? — Dave Thomas <Dave@...> 2000/08/25

Robert Feldt <feldt@ce.chalmers.se> writes:

[#4623] Re: RubyUnit testcase run for different init params? — Robert Feldt <feldt@...> 2000/08/28

On Sat, 26 Aug 2000, Dave Thomas wrote:

[#4652] Andy and Dave's European Tour 2000 — Dave Thomas <Dave@...>

24 messages 2000/08/30
[#4653] Re: Andy and Dave's European Tour 2000 — matz@... (Yukihiro Matsumoto) 2000/08/30

Hi,

[#4657] Ruby tutorials for newbie — Kevin Liang <kevin@...> 2000/08/30

Hi,

[ruby-talk:04508] Re: methods w/ ! giving nil

From: matz@... (Yukihiro Matsumoto)
Date: 2000-08-18 15:50:13 UTC
List: ruby-talk #4508
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.

							matz.

In This Thread