Yup - I realize now I was using an older version of Any::Moose. The
newest one works.
To be complete, I still ought to run all my tests twice, once with
Mouse and once with Moose. (But it's better than testing all the
combinations!) Any creative ideas on how to arrange that, beyond the
obvious duplication of all test files?
Jon
On Feb 27, 2009, at 10:17 PM, Sartak wrote:
Hi Jonathan,
On Fri, Feb 27, 2009 at 7:27 PM, Jonathan Swartz <swa...@pobox.com>
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.
This is certainly an issue that we ran into with Squirrel. One of the
reasons I wrote Any::Moose (other than having the far better name) was
to address this issue.
Once Any::Moose chooses Moose or Moose at runtime, it will continue to
use the same backer. If you find that's not the case please let me
know.
There's a test in Any::Moose to ensure this happens:
http://tinyurl.com/bgyzvf . Notice how on line 27 Moose is loaded, but
the line 32 Any::Moose still gives you Mouse.
Shawn