[#4766] Wiki — "Glen Stampoultzis" <trinexus@...>

21 messages 2000/09/04
[#4768] RE: Wiki — "NAKAMURA, Hiroshi" <nahi@...> 2000/09/04

Hi, Glen,

[#4783] Re: Wiki — Masatoshi SEKI <m_seki@...> 2000/09/04

[#4785] Re: Wiki — "NAKAMURA, Hiroshi" <nakahiro@...> 2000/09/05

Howdy,

[#4883] Re-binding a block — Dave Thomas <Dave@...>

16 messages 2000/09/12

[#4930] Perl 6 rumblings -- RFC 225 (v1) Data: Superpositions — Conrad Schneiker <schneik@...>

Hi,

11 messages 2000/09/15

[#4936] Ruby Book Eng. translation editor's questions — Jon Babcock <jon@...>

20 messages 2000/09/16

[#5045] Proposal: Add constants to Math — Robert Feldt <feldt@...>

15 messages 2000/09/21

[#5077] Crazy idea? infix method calls — hal9000@...

This is a generalization of the "in" operator idea which I

17 messages 2000/09/22

[#5157] Compile Problem with 1.6.1 — Scott Billings <aerogems@...>

When I try to compile Ruby 1.6.1, I get the following error:

15 messages 2000/09/27

[ruby-talk:5120] Re: Types and ===

From: Yasushi Shoji <yashi@...>
Date: 2000-09-26 02:25:02 UTC
List: ruby-talk #5120
At Tue, 26 Sep 2000 09:55:14 +0900,
Hal E. Fulton <hal9000@hypermetrics.com> wrote:

> Still, it bothers me a little that x==y does not always
> imply x===y. But I will just have to get used to that...

how about stating:

'===' does not imply '==' at all.  '===' is defined in each class the
way to make writing case statement easier.  most classes use '==' for
'===', but some class, such as class Class and class Range uses
other.is_a?(self) and self.include?(other), respectively.

> Actually I have trouble remembering what === means --
> whether to say x === y or y === x, which are of course
> not the same.

so, i guess you don't have to remember what '===' at all ;)

I think the moment you need to remember about '===' is when you write
your own class.  you can define '===' in your own class to control
case statement.
--
         yashi

In This Thread