[#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:6510] Range#== not defined?

From: grady@... (Steven Grady)
Date: 2000-11-21 22:40:05 UTC
List: ruby-talk #6510
Hi all.  I"m a Ruby newbie, but I've gotta say I'm really excited
about this language.  I'm definitely just starting to learn my way
around though.

My question is this: why is there no Range-specific implementation of
the "==" operator?  The obvious implementation of:
    def Range.==(other)
	first == other.first && last.other.last
    end
seems to work almost well enough.  I guess it would be better if it
handled non-Range arguments, but that should still be easy.

Is this just a lapse, or is there a good reason why Range#== has not
been defined?
--
	Steven
"The beauty of our national parks is awe-inspiring. Except for Jellystone.
I drove through there once, and it was just the same tree, rock, and picnic
bench going by in the background over and over."

In This Thread

Prev Next