The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

Search results for "module:Moose::Manual::MooseX"

Moose - A postmodern object system for Perl 5 River stage four • 2916 direct dependents • 4004 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.2207 - 21 Jan 2024 01:10:45 UTC

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 UTC

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 UTC

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 UTC

Perl::Critic::Policy::Moose::ProhibitNewMethod - Don't override Moose's standard constructors. River stage one • 4 direct dependents • 8 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 UTC

Perl::Critic::Policy::Moose::RequireCleanNamespace - Require removing implementation details from you packages. River stage one • 4 direct dependents • 8 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 UTC

Perl::Critic::Policy::Moose::ProhibitDESTROYMethod - Use DEMOLISH instead of DESTROY River stage one • 4 direct dependents • 8 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 UTC
7 results (0.046 seconds)