Comments on sartak: Moose's Metaobject Protocol: Foray

I think between B::Hooks::EndOfScope and B::Hooks:...

2009-05-18T07:51:00.000-04:00

I think between B::Hooks::EndOfScope and B::Hooks::OP::Check::StashChange we could do this pretty well - you'd use them to figure out when your file finishes or changes package and then use Devel::Declare to inject a lump of code that does the immutable call.

I'm not entirely convinced this level of magic is worth it outside of something like MooseX::Declare though.

zby, make_immutable is not the default because we ...

2009-05-17T20:44:00.000-04:00

zby, make_immutable is not the default because we simply don't know when you're done building your class. We have no useful hook for "falling off the file". There is B::Hooks::EndOfScope, but that is a compile-time hook. At the end of your class's compile-time, the only entities that have been created are subroutines. Class-building functions like "has", method modifiers, and even "extends" all take effect at runtime.

"no Moose" occurs during compile time (just like "use Moose" does) so we can't make_immutable at "no Moose" time.

I'm sure this problem can be overcome, since Moose as of a few versions ago unconditionally depends on XS.

MooseX::Declare can get away with making make_immutable the default, because it does have such a hook (which is "when the class-generator coderef returns").

I guess this question could be only justified by t...

2009-05-17T18:22:00.000-04:00

I guess this question could be only justified by the excellence (bordering on the area of magic for me) of other parts of Moose - but why this "__PACKAGE__->meta->make_immutable;" is not yet made a default?