Re: ActiveRecord: private versus protected methods

> Exactly.  That's the issue.

It's not strictly true.  Private Methods can't be called with a
receiver,  that's all.   So

class Base
  private
  def foo
    1
  end
end

class Derived < Base
  def calls_foo
    foo
  end
end

Derived.new.calls_foo will work perfectly.


> > inherited public method is not affected. Please bring up specific examples
> > (preferably as Trac tickets) and we will address them.
>
> I'm considering a fairly deep change to the way migrations work.  I'm
> looking at adding a *namespace* to migrations, so when doing a
> migration you would specify the name and version number for the
> required migration.

This sounds a little like what the engines guys have done with
migrations,  perhaps you can investigate how they implemented it?

-- 
Cheers

Koz

--~--~---------~--~----~------------~-------~--~----~
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@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to 
rubyonrails-core-unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core
-~----------~----~----~----~------~----~------~--~---