Modules are a very useful tool for organising and namespacing your code. This can be crucial on a large application. Simply saying "don't use modules" because the loading of code in modules is broken isn't really useful advice.
Cheers Luke On 5 Sep 2006, at 11:12, Thijs van der Vossen wrote: > On 5 Sep 2006, at 11:15 , Tomas Jogin wrote: >> I was experiencing some odd behaviour with my app so I decided to >> make a simple test to iron it out; I found that it is utterly >> impossible for there to be a model in the top namespace by the >> same name as another model in another different namespace. > > This has been an issue for a long time. My advice would be: Don't > Do That or even better Don't Use Modules. > > Thijs. > > -- > Fingertips - http://www.fngtps.com > > Phone: +31 (0)6 24204845 > Skype: tvandervossen > > MSN Messenger: [EMAIL PROTECTED] > iChat/AOL: [EMAIL PROTECTED] > Jabber IM: [EMAIL PROTECTED] > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
