[#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:5169] Re: Types and ===

From: matz@... (Yukihiro Matsumoto)
Date: 2000-09-28 03:12:50 UTC
List: ruby-talk #5169
Hi,

In message "[ruby-talk:5163] Re: Types and ==="
    on 00/09/28, "Hal E. Fulton" <hal9000@hypermetrics.com> writes:

|However, I'm still puzzled by two things:
|1. Why do we say "case other; when receiver" and not
|"case receiver; when other"?

I felt the case behavior should be determined by objects listed after
`when', not by a `case' object.

|2. Why is the argument order for pattern === string opposite
|from the order for string =~ pattern?

It's for historical reason (since AWK and Perl work so), but I
recommend `pattern =~ string' order in Ruby.
							matz.

In This Thread