moose

I have a big hash many levels deep, and I'd like to turn this hash into a set of Moose classes. The hash looks something like this: my %hash = ( company => { id => 1, name => 'CorpInc', departments => [ { id => 1, name => 'Sales', employees => [ { id => 1, name => 'John Smith', age => '30', }, ], }, { id => 2, name => 'IT', employees => [ { id => 2, name => 'Lucy Jones', age => '28', }, { id => 3, name => 'Miguel Cerveza', age => '25', }, ], }, ], } ); And the Moose classes: package Company; use Moose; has 'id' => (is => 'ro', isa => 'Num'); has 'name' => (is => 'ro', isa => 'Str'); has

I'm new to using Moose, but I was wondering how I can load values from a configuration file and then exposing those values as properties of my 'config' object where the attributes are the configuration names in the configuration file. For example, The configuration file might contain: server:mozilla.org protocol:HTTP So I'd like my config object to have a 'server' attribute with a value of 'mozilla.org' and a protocol attribute with a value of 'HTTP'. Right now my understanding is that I have to explicitly name the attributes with a has 'server' => ( is => 'ro', isa => 'Str', default =>

In my last question @Borodin commented my question with: You should start by removing Modern::Perl and namespace::sweep. Modules that behave as pragma should be avoided. I'm confused a bit, because: in the LATEST Moose BestPractices manual recommending to use namespace::autoclean . The use namespace::autoclean bit is simply good code hygiene, as it removes imported symbols from your class's namespace at the end of your package's compile cycle, including Moose keywords. Once the class has been built, these keywords are not needed. (This is preferred to placing no Moose at the end of your

I'm using Moose (specifically MooseX::Declare ) to create an iterator object, Iter which has a next method that advances state and returns 0 or 1 as required for use in a while statement. The problem I'm running into is that depending on the existence of one of the construction parameters, next needs to perform two very different sets of operations. The way I see it I have five options: if ... then in next method subclass hash dispatch symbol table manipulation put methods in different modules and load required one at construction time Number 1 is just amateur. Number 2 is, I suppose, the

I am currently planning the design for a new system I will need to code that interacts with a back-end API. I was contemplating object composition and inheritance and decided that the most correct procedure in my situation would be to go with composition over inheritance as my objects have a "has a" relationship to one another and not an "is a". I find now though that because some objects are reliant on other, there may be cases were "object A" has an attribute which is "object B" and an attribute "object C" - however "object B" also has an attribute "object C". In hope that this analogy would

I'm beginning to realize that this is for beginners: package Bad; has 'arr' => ( is => 'rw', 'ArrayRef[Str]' ); package main; my $bad = Bad->new(arr => [ "foo", "bar" ]); print $bad->arr->[0], "\n"; Enter traits. I'm underwhelmed by the traits API, though. Have I misunderstood something? Can I get this API instead somehow? : print $bad->arr->get(0), "\n"; Details Review the canonical traits example from Moose::Meta::Attribute::Native::Trait::Array package Stuff; use Moose; has 'options' => ( traits => ['Array'], is => 'ro', isa => 'ArrayRef[Str]', default => sub { [] }, handles => { all

Many standard modules are all using straight up perl -- problem is these guys arent using Moosey stuff, so I catch myself wrapping them with Moose or reinventing some simple functions in bigger libraries for convenience. I wondered if there was any general approach to how developers using Moose incorporate other libraries that are non-Moose. Being new to Perl and Moose I'd like to have a better understanding of how Moose is used in situations like this, or when it is generally preferred to use Moose vs Perl or even MooseX, or some other package, or whether its arbitrary. Seems like there are