If the optional gem is common, why not a config.optional_gem method? Covers all bases explicitly and succinctly.
On Sat, Sep 20, 2008 at 10:58 PM, Damian Janowski <[EMAIL PROTECTED] > wrote: > > On Sat, Sep 20, 2008 at 10:29 PM, Xavier Noria <[EMAIL PROTECTED]> wrote: > > I am for sure +1 on failing hard and handling your occasional optional > > library with Ruby code anyway. > > +1 for failing hard. If your application is smart enough to fall back > on an alternative behavior, rescue the exception and continue. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
