Update: if one removes this line from MyApp::Export:
also => [ qw(Moose) ],
... and adds "use Moose;" to MyApp::Foo, things work fine (well rather,
code execution gets up to "Undefined subroutine
&MooseX::Aliases::_get_method_metaclass called at..." which is expected
because the methods in MooseX::Aliases weren't defined in this contrived
example.
Therefore, this looks to be a bug? I would expect it should be possible to
bring in Moose via the "also" field without altering any other behaviour.
PS. some of the documentation in Moose::Exporter and
Moose::Cookbook::Extending::Recipe1 still refer to pre-0.93 class and field
names, e.g. apply_metaclass_roles(), attribute_metaclass_roles,
constructor_class_roles.
On Fri, Jan 22, 2010 at 01:15:39PM -0800, Karen Etheridge wrote:
> What is missing from this simple example?
<snip>
--
"Errors, like straws, upon the surface flow; He who would
search for pearls must dive down below." - John Dryden
. . . . .
Karen Etheridge, [email protected] GCS C+++$ USL+++$ P+++$ w--- M++
http://etheridge.ca/ PS++ PE-- b++ DI++++ e++ h(-)
