On Sep 24, 5:40 pm, MaggotChild <[email protected]> wrote: > write_attribute is at the top of the call stack so I'd think it's > going to use the most recent definition. Unless some other module > redefined write_attribute within the scope of active AR::Base (as > apposed to including it via a module) -which is possible.
Yes, this is what happens, the alias is performed in a class_eval block giving it presidency over my attempted override in the module. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
