Comments on: Perl Module Monday: namespace::autoclean

By: perigrin

perigrin — Mon, 01 Aug 2011 23:48:33 +0000

You’d think that there would be plenty of cases where CMOP was used without Moose. Turns out that after 4+ years, there wasn’t. The division between the two was leading to complexity that was making developing on either one more difficult.

That said people in the Moose community are working on a core MOP for Perl that should make things like namespace::autoclean easier to write without depending on Moose.

By: rjray

rjray — Mon, 01 Aug 2011 02:28:21 +0000

Well, that’s unfortunate. I didn’t realize that Class::MOP had been merged into Moose. I wonder why they would merge that way, as I can imagine plenty of cases where Class::MOP would be useful on its own, without Moose.

By: Jay

Jay — Sun, 31 Jul 2011 20:46:06 +0000

Unfortunately, ‘install namespace::autoclean’ is now just another way of writing ‘install Moose’ since it depends on Class::MOP which is now merged into Moose.

By: Tobi

Tobi — Wed, 27 Jul 2011 08:39:29 +0000

Or even shorter:

package Foo;
use Moose;
# use namespace::autoclean;
1;

package main;
my $foo = Foo->new();
$foo->has(); # Without namespace::autoclean, Moose’s has() method remains available in Foo’s namespace.
1;

By: Tobi

Tobi — Wed, 27 Jul 2011 08:29:18 +0000

Here’s a short example to illustrate namespace::autoclean:

package Foo;

use Moose;
use Digest::MD5 qw/ md5_hex /;
# use namespace::autoclean;

package main;

my $foo = Foo->new();

# Without the above “use namespace::autoclean”
# the following will work (but really shouldn’t).
# Un-comment “use namespace::autoclean” and all
# imported methods (md5_hex in this case) will be
# removed from Foo’s namespace.
$foo->md5_hex();