Moose - A postmodern object system for Perl 5 River stage four • 2997 direct dependents • 4448 total dependents

Moose is an extension of the Perl 5 object system. The main goal of Moose is to make Perl 5 Object Oriented programming easier, more consistent, and less tedious. With Moose you can think more about what you want to do and less about the mechanics of...

ETHER/Moose-2.2012 - 22 Nov 2019 19:07:14 GMT

Moose::Role - The Moose Role River stage four • 2997 direct dependents • 4448 total dependents

The concept of roles is documented in Moose::Manual::Roles. This document serves as API documentation....

ETHER/Moose-2.2012 - 22 Nov 2019 19:07:14 GMT

Array::To::Moose - Build Moose objects from a data array River stage zero No dependents

As shown in the above examples, the general usage is: package MyClass; use Moose; (define Moose object(s)) ... use Array::To::Moose; ... my $data_ref = selectall_arrayref($sql); # for example my $object_ref = array_to_moose( data => $data_ref desc =>...

SAMB/Array-To-Moose-v0.0.9 - 21 Sep 2015 22:24:50 GMT

Moose::Exception - Superclass for Moose internal exceptions River stage four • 2997 direct dependents • 4448 total dependents

This class contains attributes which are common to all Moose internal exception classes....

ETHER/Moose-2.2012 - 22 Nov 2019 19:07:14 GMT

MooseX::RememberHistory - Add the ability for attributes to remember their history River stage zero No dependents

MooseX::RememberHisory provides an attribute trait ("RememberHistory") which will automagically store the values of that attribute in a related ArrayRef on each write to the trait....

JBERGER/MooseX-RememberHistory-0.001 - 01 Apr 2012 18:00:32 GMT

Moose::Meta::Attribute - The Moose attribute metaclass River stage four • 2997 direct dependents • 4448 total dependents

This class is a subclass of Class::MOP::Attribute that provides additional Moose-specific functionality. To really understand this class, you will need to start with the Class::MOP::Attribute documentation. This class can be understood as a set of ad...

ETHER/Moose-2.2012 - 22 Nov 2019 19:07:14 GMT

Elastic::Model::TypeMap::Moose - Type maps for core Moose types River stage one • 1 direct dependent • 1 total dependent

Elastic::Model::TypeMap::Moose provides mapping, inflation and deflation for the core Moose::Util::TypeConstraints and MooseX::Type::Moose types. It is loaded automatically by Elastic::Model::TypeMap::Default. Definitions are inherited from parent ty...

DRTECH/Elastic-Model-0.52 - 19 Nov 2015 16:37:52 GMT

Lab::Moose::Instrument::OI_ITC503 - Oxford Instruments ITC503 Intelligent Temperature Control River stage zero No dependents

By default, two temperature sensors are used: Sensor 2 for temperatures below 1.5K and sensor 3 for temperatures above 1.5K. The used sensors can be set in the constructor, e.g. my $itc = instrument( ... high_temp_sensor => 2, low_temp_sensor => 3 );...

AKHUETTEL/Lab-Measurement-3.691 - 14 Nov 2019 19:09:40 GMT

MooseX::Types::Moose::MutualCoercion - Mutual coercions for common type constraints of Moose River stage zero No dependents

This module packages several Moose::Util::TypeConstraints with coercions, designed to mutually coerce with the built-in and common types known to Moose....

MORIYA/MooseX-Types-Moose-MutualCoercion-0.04 - 24 Dec 2013 16:52:20 GMT

Perl::Critic::Policy::Moose::ProhibitLazyBuild - Avoid lazy_build River stage one • 4 direct dependents • 9 total dependents

" lazy_build =" 1 > seemed like a good idea at the time, but it creates problems (see here <https://metacpan.org/pod/distribution/Moose/lib/Moose/Manual/BestPracti ces.pod#Avoid-lazy_build>). This policy will complain if it finds lazy_build => 1 in y...

DROLSKY/Perl-Critic-Moose-1.05 - 12 Sep 2016 17:20:06 GMT

Perl::Critic::Policy::Moose::ProhibitNewMethod - Don't override Moose's standard constructors. River stage one • 4 direct dependents • 9 total dependents

Overriding "new()" on a Moose class causes a number of problems, including speed issues and problems with order of invocation of constructors when multiple inheritance is involved. Use "BUILDARGS()" and "BUILD()" instead....

DROLSKY/Perl-Critic-Moose-1.05 - 12 Sep 2016 17:20:06 GMT

Perl::Critic::Policy::Moose::RequireCleanNamespace - Require removing implementation details from you packages. River stage one • 4 direct dependents • 9 total dependents

Anything in your namespace is part of your interface. The Moose sugar is an implementation detail and not part of what you want to support as part of your functionality, especially if you may change your implementation to not use Moose in the future....

DROLSKY/Perl-Critic-Moose-1.05 - 12 Sep 2016 17:20:06 GMT

Perl::Critic::Policy::Moose::ProhibitDESTROYMethod - Use DEMOLISH instead of DESTROY River stage one • 4 direct dependents • 9 total dependents

Getting the order of destructor execution correct with inheritance involved is difficult. Let Moose take care of it for you by putting your cleanup code into a "DEMOLISH()" method instead of a "DESTROY()" method. # ok package Foo; use Moose::Role; su...

DROLSKY/Perl-Critic-Moose-1.05 - 12 Sep 2016 17:20:06 GMT

13 results (0.025 seconds)