[#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:5125] Re: Crazy idea? infix method calls

From: Mathieu Bouchard <matju@...>
Date: 2000-09-26 03:35:37 UTC
List: ruby-talk #5125
> Since it mimics an operator, it will have to have a precedence.
> That's all that comes to my mind. If I had had more sleep last
> night, I might have an opinion about high versus low... :)
> Presumably we could fix it so that for all operaors op1 and op2,
> a op1 b in c op2 d  would mean the same as the expression
> a op1 c.include?(b) op2 d.
> Does anyone but me like this proposal at all?

let's say that there are 5 classes of precedence

1. the very high: :: []
2. operators on objects, that return objects
3. operators on objects, that return booleans (predicates: comparisons)
4. operators on booleans, that return booleans (logic)
5. the rest (interval, assignment, the very-low-prec logic)

then 'in' would fit in #3. I'd tend to say at exactly the same level as
the pattern match (=~ !~) operators in particular.

matju


In This Thread