Sartak had talked about possible adding a feature to Any::Moose to force one of the other (Mouse or Moose) not sure if that has been done though.

- Stevan


On Feb 27, 2009, at 7:27 PM, Jonathan Swartz wrote:

(resent - first attempt seemed to have gotten lost)

I'm thinking of switching the CHI distribution from Moose to Any::Moose, as a way to reduce install dependencies and overhead. The Mouse feature set is adequate for my needs.

But I realized that classes could get split between Moose and Mouse depending on if/when Moose was loaded. e.g.

 #!/usr/bin/perl
 use CHI;
 use CHI::Driver::File;         # This will use Mouse
 ...
 use Some::Module::That::Uses::Moose;
 ...
 use CHI::Driver::Memcached;    # This will use Moose

In practice, CHI driver classes get loaded on the fly as caches are created with those drivers, so it isn't an option to preload all of them.

Is it a problem for related classes to be split arbitrarily between Mouse and Moose? Could it present a testing nightmare of having to test all the possible combinations? Or are Moose and Mouse so compatible that it doesn't matter (other than for class introspection, etc.)?

Thanks
Jon


Reply via email to