On 3/12/07, Jonathan Viney <[EMAIL PROTECTED]> wrote:
> It might be easier to change alias_method_chain to ensure that the new
> methods have the same public/private/protected status as the original one.
> Or is that not desirable?

Sounds like a good idea.

In any case, I think it's good practice to be consistent, so the patch
is applied.

jeremy

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to