On Sep 5, 2007, at 3:36 AM, Brian Candler wrote: > This gives users of Merb three options: > - don't use core extensions > - use Merb's core extensions plugin > - use someone else's core extensions (e.g. ActiveSupport), which > may be > necessary in the case where an ORM depends on it (e.g. ActiveRecord) > > Comments?
Bah.. got trigger happy with the send button. Just to complete my thought: I'm not opposed to that library living in an insular namespace for internal use so it wouldn't collide with ActiveSupport or Facets. But when it gets down to brass tacks, as a developer of merb, I'd still like to have our own internal lib of methods I can rely on to behave in a certain manner. -- Stephen Caudill (voxdolo) _______________________________________________ Merb-devel mailing list Merb-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/merb-devel
