5 ms·

> so what is an attribute, what is a method call It's all method calls. Attributes don't really exist.

• xentronium 12y ago
  Well, they sort of do, in the form of instance variables.
  • regularfry 12y ago
    Ish. In the context of the GP's point, they aren't a problem because the syntax to access them is distinct.
  • deleted 12y ago
    [deleted]
• epidemian 12y ago
  > It's all method calls. Probably nitpicking, but it's actually all messages. An object might not have a method "foo", but happily respond to the "foo" message.
  • dragonwriter 12y ago
    Its all method calls. Specifically, its all calls to #send, most of which get relayed to another method (either based on the message name or, if no such method exists, #method_missing.)
  • throwaway0010 12y ago
    And the object responds to the "foo" message by calling a method. The difference is whether we're discussing the invocation or the response. OP's usage of method isn't incorrect in this case if it's discussing the response. It is true that all message responses (including accessors) are implemented using methods.
    • epidemian 12y ago
      > It is true that all message responses (including accessors) are implemented using methods. An object can respond to a message even though it doesn't have a method with that name. A classic example are Rails' dynamic finders: User.methods.include?(:find_by_name) => false User.respond_to?(:find_by_name) => true
      • dragonwriter 12y ago
        > An object can respond to a message even though it doesn't have a method with that name. Sure, by using a different method (method_missing); its still all method calls.
      • throwaway0010 12y ago
        Yes and the responses are implemented with methods. Always.
• dasil003 12y ago
  I believe he meant local variables (or if he didn't he should have).