Wouldn't it be preferable to avoid basing the default behavior on the mere existence of a class?
It could easily bite back, in case a ruby gem you use (or one of its dependencies) defines such a class. (Note that I'm personally very happy to get exceptions when the subject is nil, or to use try or similar helpers when I do not want that) -- Thibaut -- 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.
