[#6363] Re: rescue clause affecting IO loop behavior — ts <decoux@...>

>>>>> "D" == David Alan Black <dblack@candle.superlink.net> writes:

17 messages 2000/11/14
[#6367] Re: rescue clause affecting IO loop behavior — David Alan Black <dblack@...> 2000/11/14

Hello again --

[#6582] best way to interleaf arrays? — David Alan Black <dblack@...>

Hello --

15 messages 2000/11/26

[#6646] RE: Array Intersect (&) question — Aleksi Niemel<aleksi.niemela@...>

Ross asked something about widely known and largely ignored language (on

23 messages 2000/11/29
[#6652] RE: Array Intersect (&) question — rpmohn@... (Ross Mohn) 2000/11/29

aleksi.niemela@cinnober.com (Aleksi Niemel) wrote in

[#6723] Re: Array Intersect (&) question — Mathieu Bouchard <matju@...> 2000/12/01

> >Use a hash. Here's code to do both and more. It assumes that

[#6656] printing/accessing arrays and hashes — raja@... (Raja S.)

I'm coming to Ruby with a Python & Common Lisp background.

24 messages 2000/11/30

[ruby-talk:6604] Re: Question on sort!

From: matz@... (Yukihiro Matsumoto)
Date: 2000-11-28 14:22:04 UTC
List: ruby-talk #6604
Hi,

In message "[ruby-talk:6601] Re: Question on sort!"
    on 00/11/28, Dave Thomas <Dave@thomases.com> writes:

|> This is very preliminary behavior following
|> a-bang-method-returns-nil-if-it-does-not-modify-the-recevier
|> principle.  The behavior shall be more thorough in the future.
|
|Although I see the reason for returning nil on methods such as gsub!,
|is there really any practical reason for doing so on sort! or
|reverse! ? This seems to me to be more of an inconvenience than a help, 
|and I'm not sure that any program would have a use for the test.|
|However, I can see a lot of potential problems with programs that try
|to be efficient and sort (or reverse) in place.
|
|   ary.sort!.reverse!.each {...
|
|It works fine 99.999% of the time, but occasionally fails with some
|message about some undefined method and nil...
|
|Perhaps we're extending the wrong principle here. Just because _some_
|! methods return nil, should all of them?

OK, OK.  Let's discuss.

The principle above have both pro and con.

  (+) consistency.
  (-) returning nil somtimes breaks method chains.

The latter can be avoided if one follows the no-bang-method-chain
rule.  But I don't force you to agree with me (yet ;-).

							matz.

In This Thread