| Name : perl-MooseX-Role-Parameterized
| |
| Version : 1.10
| Vendor : obs://build_opensuse_org/home:sbahling
|
| Release : 2.2
| Date : 2018-06-20 02:38:28
|
| Group : Development/Libraries/Perl
| Source RPM : perl-MooseX-Role-Parameterized-1.10-2.2.src.rpm
|
| Size : 0.08 MB
| |
| Packager : (none)
| |
| Summary : Moose roles with composition parameters
|
Description :
Your parameterized role consists of two new things: parameter declarations
and a \'role\' block.
Parameters are declared using the parameter keyword which very much
resembles Moose/has. You can use any option that Moose/has accepts. The
default value for the \'is\' option is \'ro\' as that\'s a very common case. Use
\'is => \'bare\'\' if you want no accessor. These parameters will get their
values when the consuming class (or role) uses Moose/with. A parameter
object will be constructed with these values, and passed to the \'role\'
block.
The \'role\' block then uses the usual Moose::Role keywords to build up a
role. You can shift off the parameter object to inspect what the consuming
class provided as parameters. You use the parameters to customize your role
however you wish.
There are many possible implementations for parameterized roles (hopefully
with a consistent enough API); I believe this to be the easiest and most
flexible design. Coincidentally, Pugs originally had an eerily similar
design.
See MooseX::Role::Parameterized::Extending for some tips on how to extend
this module.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/home:/sbahling:/Backports:/SLE-15/SLE_15/noarch |
Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server
Provides :
perl(MooseX::Role::Parameterised)
perl(MooseX::Role::Parameterized)
perl(MooseX::Role::Parameterized::Meta::Role::Parameterized)
perl(MooseX::Role::Parameterized::Meta::Trait::Parameterizable)
perl(MooseX::Role::Parameterized::Meta::Trait::Parameterized)
perl(MooseX::Role::Parameterized::Parameters)
perl-MooseX-Role-Parameterized
Requires :
