moose

I'm having a really hard time understanding the intersection of OO Perl and my $self = shift; The documentation on these individual elements is great, but none of them that I've found touch on how they work together. I've been using Moose to make modules with attributes, and of course, it's useful to reference a module's attribute within said module. I've been told over and over again to use my $self = shift; within a subroutine to assign the module's attributes to that variable. This makes sense and works, but when I'm also passing arguments to the subroutine, this process clearly takes the

I am trying to make an extensible system whereby I can code up a new module to be a handler. I want the program to automatically load any new .pm file that is put into the Handlers directory and conforms to a Moose::Role interface. I'm wondering whether there is a Perl module or a more Moose sanctioned way to do this automatically? Here is what I have built so far, but it seems a little verbose and there has got to be a simpler way to do it. handler.pl contains: #!/usr/bin/perl use Handler; use Data::Dumper; my $base_handler = Handler->new(); $base_handler->load_modules('SysG/Handler'); print

I want to create a generic class, whose builder would not return an instance of this generic class, but an instance of a dedicated child class. As Moose does automatic object building, I do not get to understand if this something possible, and how to create a Moose class with Moose syntax and having this behaviour. e.g.: The user asks: $file = Repository->new(uri=>'sftp://blabla') .... and is returned an `Repository::_Sftp`` instance User would use $file as if it is a Repository instance, without the need to know the real subclass (polymorphism) Note: As requested, maybe i should have been

I was usually using Storable with nstore , but now I have a module that has CODE and apparently Storable doesn't like that. I found YAML (and YAML::XS which I can't really get to work ). I also experimented a bit with MooseX::Storage without much success. Are there other alternatives? What would you recommend? Ether You can dump a coderef with Data::Dumper after setting $Data::Dumper::Deparse to a true value, but this is only intended for debugging purposes, not for serialization. I would suggest you go back to looking at why MooseX::Storage isn't working out for you, as the authors tried

The following script p.pl works fine: use feature qw(say); use strict; use warnings; use lib '.'; use P1; my $obj = P1->new(name => 'John'); say "The name is: ", $obj->name; where the class P1 is defined in file P1.pm : package P1; use Moose; has name => (is => 'rw', isa => 'Str'); 1; However, when I try to move the class P1.pm into the main script: #! /usr/bin/env perl use feature qw(say); use strict; use warnings; my $obj = P1->new(name => 'John'); say "The name is: ", $obj->name; package P1; use Moose; has name => (is => 'rw', isa => 'Str'); I get error: Can't locate object method "name"