Lars Pind wrote: > Hi Nicholas > > Is there a strict one-file-to-one-class convention now?
Yea, pretty much. Instead we could use the file's path to find the module into which it should load things (a/b/c.rb => A::B) and then get a list of constants before and after we load the file. Comparing the lists will tell us what that file loaded, and then we could mark all the constants for future removal. This gets a little harder given that one file can load another file which may load another. PDI. ;-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
