Thanks, but, really, that's not advice at all. Advice would be to offer a different solution to contextual and/or same-named identifiers, compartmentalized features, functionality and so forth -- the very problem that the use of namespaces solves.
Furthermore, namespaces, unlike the goto-statement and similar things you "shouldn't do" in programming, aren't thought of as "harmful" practices in general. It's just within Rails that namespaces are frowned upon, and, IMHO, for no good reason (the only semi-logical reason I can find is: "we can't seem to get 'em right"). Note that I'm NOT casting any blame here, nor expecting any favors or service; I'm just rejecting the IMHO baseless proposition to "not use" modules in favor of, well... in favor of nothing else. Namespaces aren't evil, not at all. There is absolutely nothing wrong with using namespaces in general. It's too bad that they just don't work very well in Rails (but much better now than previously, of course). Best regards, Tomas Jogin On 9/5/06, Thijs van der Vossen <[EMAIL PROTECTED]> 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 -~----------~----~----~----~------~----~------~--~---
