2009/4/16 Daniel Parker <[email protected]>: > Is there a goal for Extlib to be compatible with ActiveSupport? If so, I can > help fix these problems. At the very least, Extlib could refrain from > defining certain methods when it detects ActiveSupport has already been > loaded.
The whole reason why Extlib exists is because ActiveSupport as it is now loads and monkey patches a little bit too much. It even loads up Memcache Client and Builder via ./vendor whether you like it or not, when you require 'activesupport' — go check the source. This is why I added activesupport/mini for Rails 3, and also tried to port LazyArray, a class DM core is built on, to Test::Unit, but it is a lot of boring work, to rewrite several thousands of lines of code from RSpec to Test::Unit. So if you want to help, right way to do it is to fix ActiveSupport once and for all, move rails specific dependencies from it into rails_support, and port LazyArray, LazyModule and a few other useful things from RSpec to T::U so then can be included into ActiveSupport. Then extlib won't really be needed. But this change won't happen over night, because Merb also uses Extlib, and there is one more compatibility problem to be aware of: ActiveSupport does not use JSON gem, and provides own JSON serialization that is tied to the way ActiveRecord works. So before Merb 1.x could be moved to AS, this is another problem to be solved. -- MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
