Thanks for the clarification everyone! I wouldn't have expected it to have different meaning depending on he object/class type. I'll keep an eye out for that.
On Aug 12, 9:40 am, Marnen Laibow-Koser <rails-mailing-l...@andreas- s.net> wrote: > Frederick Cheung wrote: > > On Aug 12, 4:37 pm, Marnen Laibow-Koser <rails-mailing-l...@andreas- > > s.net> wrote: > >> are methods in Ruby. Not all methods are operators, but that's another > >> syntactic issue. > > > If we're being pedantic, then not all operators are methods: ! is not > > a method, nor is ?: and != is hardwired to be the negation of == > > (there are a few others eg &&, :: et.) > > Ack, you're right. I keep forgetting that unlike Smalltalk or C++, not > *every* operator is a method call. Sorry about the error. (However, << > *is* both.) > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > mar...@marnen.org > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
