On Fri, Sep 5, 2008 at 4:47 AM, Xavier Noria <[EMAIL PROTECTED]> wrote:
> If there's no admin.rb you can just create an Admin module on the fly > and go on, but if there's one you should load it. > > And that doesn't fit because a user would expect to be able to use > constants in admin.rb and there's no guarantee those are ready for > autoloading because we are in the middle of the recursion. I thought about rescueing NameError and deferring those loads until they would eventually resolve by themselves, but admin.rb and admin_prime.rb could point to each other and that wouldn't be solvable. But I've seen another issue: Currently initializers are able to use autoloaded constants, so that tree traversal should be done before they run. But admin.rb may assume initializers have been run. I believe this is indeed a stopper. --~--~---------~--~----~------------~-------~--~----~ 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 [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-core?hl=en -~----------~----~----~----~------~----~------~--~---
