Whilst the point is entirely valid, IMHO there is equally a sense of 'polluting' the code with loads of __ stuff. The thing I really like about ruby and rails is the nice readability factor.
I have been bitten by errors, and template name clashes and the like, but coming up with an extended name in the app is usually fairly trivial. After all, you are going to inflict __ throughout every application in every situation. That would be a shame since I would have thought that in many cases problems with name conflicts occur rarely. Tonypm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
