On 23 Apr 2008, at 11:23, Michael Koziarski wrote:
> >> Can anything ugly like forcing everyting to be loaded into a >> temporary >> module (so that no one else sees it) and then 'uncloaking' when we're >> finished. Sounds like it would just be over the top compared to just >> loading everything. > > Yeah, and it's more an issue with ruby rather than something we should > try to work around. After all: > > class Foo > def Foo.some_class_method > end > end > > So does anyone want to take a stab at a dependencies mechanism which > just loads everything and has regular const_missing behaviour if it > hits something it doesn't understand? I'll take a shot at it, but I won't have time for a few days Fred --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
