Philip Hallstrom wrote in post #992605: >> end > Using a method would let one override what happens when you assign to > that attribute.. say you need to do something magical with it... > validate it... convert it... set something else somewhere else... that > sort of thing...
And, just as importantly, the method provides encapsulation, effectively hiding the internal implementation from the public API. This provides the flexibility of modifying or improving the internal implementation without affecting the consumers of the class. -- Posted via http://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.
