On 05.01.2009 10:58, Brian Candler wrote:
> There aren't really any operators in Ruby. Ruby simply maps all these to 
> method calls (*), so to find out what the operator *means* you have to 
> look at the class documentation for that method.

> The only real purpose of the operator precedence table is to show how 
> expressions containing multiple operators are resolved. e.g.

Brian, you are contradicting yourself: first you deny the presence of 
operators in Ruby and then you talk about them nevertheless. :-)

Fact is, there _are_ operators in Ruby - and they do have a precedence. 
   (I am not sure why you put an "only" into the sentence above - 
operator precedence is what a precedence table is about.)

Fact is also, that their semantics are defined via methods.  Note also 
that for understanding the semantics of most binary operators the method 
#coerce plays a crucial role (=> double dispatch).

Kind regards

	robert

-- 
remember.guy do |as, often| as.you_can - without end