| File | /usr/local/lib/perl5/site_perl/5.10.1/darwin-2level/Moose.pm |
| Statements Executed | 170 |
| Statement Execution Time | 4.92ms |
| Calls | P | F | Exclusive Time |
Inclusive Time |
Subroutine |
|---|---|---|---|---|---|
| 1 | 1 | 1 | 3.49ms | 172ms | Moose::BEGIN@14 |
| 1 | 1 | 1 | 2.68ms | 13.1ms | Moose::BEGIN@26 |
| 1 | 1 | 1 | 2.64ms | 21.5ms | Moose::BEGIN@18 |
| 1 | 1 | 1 | 1.42ms | 2.73ms | Moose::BEGIN@11 |
| 1 | 1 | 1 | 1.39ms | 17.2ms | Moose::BEGIN@19 |
| 1 | 1 | 1 | 1.37ms | 2.88ms | Moose::BEGIN@24 |
| 1 | 1 | 1 | 1.36ms | 1.92ms | Moose::BEGIN@29 |
| 1 | 1 | 1 | 1.27ms | 59.7ms | Moose::BEGIN@20 |
| 1 | 1 | 1 | 947µs | 1.99ms | Moose::BEGIN@30 |
| 1 | 1 | 1 | 800µs | 2.09ms | Moose::BEGIN@27 |
| 1 | 1 | 1 | 741µs | 968µs | Moose::BEGIN@31 |
| 1 | 1 | 1 | 664µs | 1.37ms | Moose::BEGIN@28 |
| 1 | 1 | 1 | 344µs | 1.39ms | Moose::BEGIN@37 |
| 1 | 1 | 1 | 337µs | 858µs | Moose::BEGIN@32 |
| 1 | 1 | 1 | 310µs | 350µs | Moose::BEGIN@12 |
| 1 | 1 | 1 | 188µs | 299µs | Moose::BEGIN@22 |
| 8 | 5 | 2 | 99µs | 10.2ms | Moose::has |
| 1 | 1 | 1 | 71µs | 1.52ms | Moose::init_meta |
| 1 | 1 | 1 | 33µs | 33µs | Moose::BEGIN@5 |
| 1 | 1 | 1 | 16µs | 19µs | Moose::BEGIN@2 |
| 1 | 1 | 2 | 15µs | 15µs | Moose::bootstrap (xsub) |
| 1 | 1 | 1 | 13µs | 30µs | Moose::BEGIN@16 |
| 1 | 1 | 1 | 10µs | 1.31ms | Moose::BEGIN@34 |
| 1 | 1 | 1 | 9µs | 26µs | Moose::BEGIN@3 |
| 1 | 1 | 1 | 5µs | 5µs | Moose::BEGIN@21 |
| 1 | 1 | 1 | 4µs | 4µs | Moose::BEGIN@35 |
| 0 | 0 | 0 | 0s | 0s | Moose::__ANON__[:221] |
| 0 | 0 | 0 | 0s | 0s | Moose::_get_caller |
| 0 | 0 | 0 | 0s | 0s | Moose::after |
| 0 | 0 | 0 | 0s | 0s | Moose::around |
| 0 | 0 | 0 | 0s | 0s | Moose::augment |
| 0 | 0 | 0 | 0s | 0s | Moose::before |
| 0 | 0 | 0 | 0s | 0s | Moose::extends |
| 0 | 0 | 0 | 0s | 0s | Moose::inner |
| 0 | 0 | 0 | 0s | 0s | Moose::override |
| 0 | 0 | 0 | 0s | 0s | Moose::super |
| 0 | 0 | 0 | 0s | 0s | Moose::throw_error |
| 0 | 0 | 0 | 0s | 0s | Moose::with |
| Line | State ments |
Time on line |
Calls | Time in subs |
Code |
|---|---|---|---|---|---|
| 1 | package Moose; | ||||
| 2 | 3 | 25µs | 2 | 23µs | # spent 19µs (16+3) within Moose::BEGIN@2 which was called
# once (16µs+3µs) by SimpleDB::Client::BEGIN@46 at line 2 # spent 19µs making 1 call to Moose::BEGIN@2
# spent 3µs making 1 call to strict::import |
| 3 | 3 | 25µs | 2 | 44µs | # spent 26µs (9+17) within Moose::BEGIN@3 which was called
# once (9µs+17µs) by SimpleDB::Client::BEGIN@46 at line 3 # spent 26µs making 1 call to Moose::BEGIN@3
# spent 17µs making 1 call to warnings::import |
| 4 | |||||
| 5 | 3 | 76µs | 1 | 33µs | # spent 33µs within Moose::BEGIN@5 which was called
# once (33µs+0s) by SimpleDB::Client::BEGIN@46 at line 5 # spent 33µs making 1 call to Moose::BEGIN@5 |
| 6 | |||||
| 7 | 1 | 800ns | our $VERSION = '0.98'; | ||
| 8 | 1 | 16µs | $VERSION = eval $VERSION; | ||
| 9 | 1 | 400ns | our $AUTHORITY = 'cpan:STEVAN'; | ||
| 10 | |||||
| 11 | 3 | 112µs | 2 | 2.79ms | # spent 2.73ms (1.42+1.31) within Moose::BEGIN@11 which was called
# once (1.42ms+1.31ms) by SimpleDB::Client::BEGIN@46 at line 11 # spent 2.73ms making 1 call to Moose::BEGIN@11
# spent 63µs making 1 call to Exporter::import |
| 12 | 3 | 307µs | 2 | 389µs | # spent 350µs (310+39) within Moose::BEGIN@12 which was called
# once (310µs+39µs) by SimpleDB::Client::BEGIN@46 at line 12 # spent 350µs making 1 call to Moose::BEGIN@12
# spent 39µs making 1 call to Exporter::import |
| 13 | |||||
| 14 | 3 | 106µs | 2 | 172ms | # spent 172ms (3.49+169) within Moose::BEGIN@14 which was called
# once (3.49ms+169ms) by SimpleDB::Client::BEGIN@46 at line 14 # spent 172ms making 1 call to Moose::BEGIN@14
# spent 22µs making 1 call to Moose::Exporter::import |
| 15 | |||||
| 16 | 3 | 48µs | 2 | 48µs | # spent 30µs (13+17) within Moose::BEGIN@16 which was called
# once (13µs+17µs) by SimpleDB::Client::BEGIN@46 at line 16 # spent 30µs making 1 call to Moose::BEGIN@16
# spent 17µs making 1 call to UNIVERSAL::VERSION |
| 17 | |||||
| 18 | 3 | 123µs | 1 | 21.5ms | # spent 21.5ms (2.64+18.9) within Moose::BEGIN@18 which was called
# once (2.64ms+18.9ms) by SimpleDB::Client::BEGIN@46 at line 18 # spent 21.5ms making 1 call to Moose::BEGIN@18 |
| 19 | 3 | 110µs | 1 | 17.2ms | # spent 17.2ms (1.39+15.8) within Moose::BEGIN@19 which was called
# once (1.39ms+15.8ms) by SimpleDB::Client::BEGIN@46 at line 19 # spent 17.2ms making 1 call to Moose::BEGIN@19 |
| 20 | 3 | 801µs | 1 | 59.7ms | # spent 59.7ms (1.27+58.4) within Moose::BEGIN@20 which was called
# once (1.27ms+58.4ms) by SimpleDB::Client::BEGIN@46 at line 20 # spent 59.7ms making 1 call to Moose::BEGIN@20 |
| 21 | 3 | 19µs | 1 | 5µs | # spent 5µs within Moose::BEGIN@21 which was called
# once (5µs+0s) by SimpleDB::Client::BEGIN@46 at line 21 # spent 5µs making 1 call to Moose::BEGIN@21 |
| 22 | 3 | 110µs | 1 | 299µs | # spent 299µs (188+111) within Moose::BEGIN@22 which was called
# once (188µs+111µs) by SimpleDB::Client::BEGIN@46 at line 22 # spent 299µs making 1 call to Moose::BEGIN@22 |
| 23 | |||||
| 24 | 3 | 716µs | 1 | 2.88ms | # spent 2.88ms (1.37+1.51) within Moose::BEGIN@24 which was called
# once (1.37ms+1.51ms) by SimpleDB::Client::BEGIN@46 at line 24 # spent 2.88ms making 1 call to Moose::BEGIN@24 |
| 25 | |||||
| 26 | 3 | 148µs | 1 | 13.1ms | # spent 13.1ms (2.68+10.4) within Moose::BEGIN@26 which was called
# once (2.68ms+10.4ms) by SimpleDB::Client::BEGIN@46 at line 26 # spent 13.1ms making 1 call to Moose::BEGIN@26 |
| 27 | 3 | 155µs | 1 | 2.09ms | # spent 2.09ms (800µs+1.30) within Moose::BEGIN@27 which was called
# once (800µs+1.30ms) by SimpleDB::Client::BEGIN@46 at line 27 # spent 2.09ms making 1 call to Moose::BEGIN@27 |
| 28 | 3 | 108µs | 1 | 1.37ms | # spent 1.37ms (664µs+711µs) within Moose::BEGIN@28 which was called
# once (664µs+711µs) by SimpleDB::Client::BEGIN@46 at line 28 # spent 1.37ms making 1 call to Moose::BEGIN@28 |
| 29 | 3 | 109µs | 1 | 1.92ms | # spent 1.92ms (1.36+552µs) within Moose::BEGIN@29 which was called
# once (1.36ms+552µs) by SimpleDB::Client::BEGIN@46 at line 29 # spent 1.92ms making 1 call to Moose::BEGIN@29 |
| 30 | 3 | 102µs | 1 | 1.99ms | # spent 1.99ms (947µs+1.04) within Moose::BEGIN@30 which was called
# once (947µs+1.04ms) by SimpleDB::Client::BEGIN@46 at line 30 # spent 1.99ms making 1 call to Moose::BEGIN@30 |
| 31 | 3 | 102µs | 1 | 968µs | # spent 968µs (741+228) within Moose::BEGIN@31 which was called
# once (741µs+228µs) by SimpleDB::Client::BEGIN@46 at line 31 # spent 968µs making 1 call to Moose::BEGIN@31 |
| 32 | 3 | 100µs | 1 | 858µs | # spent 858µs (337+520) within Moose::BEGIN@32 which was called
# once (337µs+520µs) by SimpleDB::Client::BEGIN@46 at line 32 # spent 858µs making 1 call to Moose::BEGIN@32 |
| 33 | |||||
| 34 | 3 | 27µs | 2 | 2.61ms | # spent 1.31ms (10µs+1.30) within Moose::BEGIN@34 which was called
# once (10µs+1.30ms) by SimpleDB::Client::BEGIN@46 at line 34 # spent 1.31ms making 1 call to Moose::BEGIN@34
# spent 1.30ms making 1 call to Moose::Exporter::__ANON__[Moose/Exporter.pm:389] |
| 35 | 3 | 19µs | 1 | 4µs | # spent 4µs within Moose::BEGIN@35 which was called
# once (4µs+0s) by SimpleDB::Client::BEGIN@46 at line 35 # spent 4µs making 1 call to Moose::BEGIN@35 |
| 36 | |||||
| 37 | 3 | 1.11ms | 1 | 1.39ms | # spent 1.39ms (344µs+1.05) within Moose::BEGIN@37 which was called
# once (344µs+1.05ms) by SimpleDB::Client::BEGIN@46 at line 37 # spent 1.39ms making 1 call to Moose::BEGIN@37 |
| 38 | |||||
| 39 | sub throw_error { | ||||
| 40 | # FIXME This | ||||
| 41 | shift; | ||||
| 42 | goto \&confess | ||||
| 43 | } | ||||
| 44 | |||||
| 45 | sub extends { | ||||
| 46 | my $meta = shift; | ||||
| 47 | |||||
| 48 | Moose->throw_error("Must derive at least one class") unless @_; | ||||
| 49 | |||||
| 50 | # this checks the metaclass to make sure | ||||
| 51 | # it is correct, sometimes it can get out | ||||
| 52 | # of sync when the classes are being built | ||||
| 53 | $meta->superclasses(@_); | ||||
| 54 | } | ||||
| 55 | |||||
| 56 | sub with { | ||||
| 57 | Moose::Util::apply_all_roles(shift, @_); | ||||
| 58 | } | ||||
| 59 | |||||
| 60 | # spent 10.2ms (99µs+10.1) within Moose::has which was called 8 times, avg 1.28ms/call:
# 4 times (69µs+5.01ms) by Moose::has at line 293 of Moose/Exporter.pm, avg 1.27ms/call
# once (12µs+2.30ms) by main::BEGIN@2 at line 88 of ../lib/SimpleDB/Client.pm
# once (6µs+1.06ms) by main::BEGIN@2 at line 102 of ../lib/SimpleDB/Client.pm
# once (6µs+902µs) by main::BEGIN@2 at line 121 of ../lib/SimpleDB/Client.pm
# once (5µs+856µs) by main::BEGIN@2 at line 134 of ../lib/SimpleDB/Client.pm | ||||
| 61 | 4 | 1µs | my $meta = shift; | ||
| 62 | 4 | 2µs | my $name = shift; | ||
| 63 | |||||
| 64 | 4 | 4µs | Moose->throw_error('Usage: has \'name\' => ( key => value, ... )') | ||
| 65 | if @_ % 2 == 1; | ||||
| 66 | |||||
| 67 | 4 | 15µs | 4 | 34µs | my %options = ( definition_context => Moose::Util::_caller_info(), @_ ); # spent 34µs making 4 calls to Moose::Util::_caller_info, avg 9µs/call |
| 68 | 4 | 5µs | my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ]; | ||
| 69 | 8 | 33µs | 4 | 4.97ms | $meta->add_attribute( $_, %options ) for @$attrs; # spent 4.97ms making 4 calls to Moose::Meta::Class::add_attribute, avg 1.24ms/call |
| 70 | } | ||||
| 71 | |||||
| 72 | sub before { | ||||
| 73 | Moose::Util::add_method_modifier(shift, 'before', \@_); | ||||
| 74 | } | ||||
| 75 | |||||
| 76 | sub after { | ||||
| 77 | Moose::Util::add_method_modifier(shift, 'after', \@_); | ||||
| 78 | } | ||||
| 79 | |||||
| 80 | sub around { | ||||
| 81 | Moose::Util::add_method_modifier(shift, 'around', \@_); | ||||
| 82 | } | ||||
| 83 | |||||
| 84 | 1 | 100ns | our $SUPER_PACKAGE; | ||
| 85 | 1 | 100ns | our $SUPER_BODY; | ||
| 86 | 1 | 200ns | our @SUPER_ARGS; | ||
| 87 | |||||
| 88 | sub super { | ||||
| 89 | # This check avoids a recursion loop - see | ||||
| 90 | # t/100_bugs/020_super_recursion.t | ||||
| 91 | return if defined $SUPER_PACKAGE && $SUPER_PACKAGE ne caller(); | ||||
| 92 | return unless $SUPER_BODY; $SUPER_BODY->(@SUPER_ARGS); | ||||
| 93 | } | ||||
| 94 | |||||
| 95 | sub override { | ||||
| 96 | my $meta = shift; | ||||
| 97 | my ( $name, $method ) = @_; | ||||
| 98 | $meta->add_override_method_modifier( $name => $method ); | ||||
| 99 | } | ||||
| 100 | |||||
| 101 | sub inner { | ||||
| 102 | my $pkg = caller(); | ||||
| 103 | our ( %INNER_BODY, %INNER_ARGS ); | ||||
| 104 | |||||
| 105 | if ( my $body = $INNER_BODY{$pkg} ) { | ||||
| 106 | my @args = @{ $INNER_ARGS{$pkg} }; | ||||
| 107 | local $INNER_ARGS{$pkg}; | ||||
| 108 | local $INNER_BODY{$pkg}; | ||||
| 109 | return $body->(@args); | ||||
| 110 | } else { | ||||
| 111 | return; | ||||
| 112 | } | ||||
| 113 | } | ||||
| 114 | |||||
| 115 | sub augment { | ||||
| 116 | my $meta = shift; | ||||
| 117 | my ( $name, $method ) = @_; | ||||
| 118 | $meta->add_augment_method_modifier( $name => $method ); | ||||
| 119 | } | ||||
| 120 | |||||
| 121 | 1 | 7µs | 1 | 755µs | Moose::Exporter->setup_import_methods( # spent 755µs making 1 call to Moose::Exporter::setup_import_methods |
| 122 | with_meta => [ | ||||
| 123 | qw( extends with has before after around override augment ) | ||||
| 124 | ], | ||||
| 125 | as_is => [ | ||||
| 126 | qw( super inner ), | ||||
| 127 | \&Carp::confess, | ||||
| 128 | \&Scalar::Util::blessed, | ||||
| 129 | ], | ||||
| 130 | ); | ||||
| 131 | |||||
| 132 | # spent 1.52ms (71µs+1.45) within Moose::init_meta which was called
# once (71µs+1.45ms) by Moose::Exporter::__ANON__[/usr/local/lib/perl5/site_perl/5.10.1/darwin-2level/Moose/Exporter.pm:389] at line 354 of Moose/Exporter.pm | ||||
| 133 | # This used to be called as a function. This hack preserves | ||||
| 134 | # backwards compatibility. | ||||
| 135 | 1 | 900ns | if ( $_[0] ne __PACKAGE__ ) { | ||
| 136 | return __PACKAGE__->init_meta( | ||||
| 137 | for_class => $_[0], | ||||
| 138 | base_class => $_[1], | ||||
| 139 | metaclass => $_[2], | ||||
| 140 | ); | ||||
| 141 | } | ||||
| 142 | |||||
| 143 | 1 | 300ns | shift; | ||
| 144 | 1 | 2µs | my %args = @_; | ||
| 145 | |||||
| 146 | 1 | 700ns | my $class = $args{for_class} | ||
| 147 | or Moose->throw_error("Cannot call init_meta without specifying a for_class"); | ||||
| 148 | 1 | 1µs | my $base_class = $args{base_class} || 'Moose::Object'; | ||
| 149 | 1 | 800ns | my $metaclass = $args{metaclass} || 'Moose::Meta::Class'; | ||
| 150 | |||||
| 151 | 1 | 9µs | 1 | 2µs | Moose->throw_error("The Metaclass $metaclass must be a subclass of Moose::Meta::Class.") # spent 2µs making 1 call to UNIVERSAL::isa |
| 152 | unless $metaclass->isa('Moose::Meta::Class'); | ||||
| 153 | |||||
| 154 | # make a subtype for each Moose class | ||||
| 155 | 1 | 5µs | 2 | 319µs | class_type($class) # spent 293µs making 1 call to Moose::Util::TypeConstraints::class_type
# spent 25µs making 1 call to Moose::Util::TypeConstraints::find_type_constraint |
| 156 | unless find_type_constraint($class); | ||||
| 157 | |||||
| 158 | 1 | 300ns | my $meta; | ||
| 159 | |||||
| 160 | 1 | 2µs | 1 | 1µs | if ( $meta = Class::MOP::get_metaclass_by_name($class) ) { # spent 1µs making 1 call to Class::MOP::get_metaclass_by_name |
| 161 | unless ( $meta->isa("Moose::Meta::Class") ) { | ||||
| 162 | my $error_message = "$class already has a metaclass, but it does not inherit $metaclass ($meta)."; | ||||
| 163 | if ( $meta->isa('Moose::Meta::Role') ) { | ||||
| 164 | Moose->throw_error($error_message . ' You cannot make the same thing a role and a class. Remove either Moose or Moose::Role.'); | ||||
| 165 | } else { | ||||
| 166 | Moose->throw_error($error_message); | ||||
| 167 | } | ||||
| 168 | } | ||||
| 169 | } else { | ||||
| 170 | # no metaclass, no 'meta' method | ||||
| 171 | |||||
| 172 | # now we check whether our ancestors have metaclass, and if so borrow that | ||||
| 173 | 1 | 10µs | 1 | 2µs | my ( undef, @isa ) = @{ $class->mro::get_linear_isa }; # spent 2µs making 1 call to mro::get_linear_isa |
| 174 | |||||
| 175 | 1 | 2µs | foreach my $ancestor ( @isa ) { | ||
| 176 | my $ancestor_meta = Class::MOP::get_metaclass_by_name($ancestor) || next; | ||||
| 177 | |||||
| 178 | my $ancestor_meta_class = ($ancestor_meta->is_immutable | ||||
| 179 | ? $ancestor_meta->_get_mutable_metaclass_name | ||||
| 180 | : ref($ancestor_meta)); | ||||
| 181 | |||||
| 182 | # if we have an ancestor metaclass that inherits $metaclass, we use | ||||
| 183 | # that. This is like _fix_metaclass_incompatibility, but we can do it now. | ||||
| 184 | |||||
| 185 | # the case of having an ancestry is not very common, but arises in | ||||
| 186 | # e.g. Reaction | ||||
| 187 | unless ( $metaclass->isa( $ancestor_meta_class ) ) { | ||||
| 188 | if ( $ancestor_meta_class->isa($metaclass) ) { | ||||
| 189 | $metaclass = $ancestor_meta_class; | ||||
| 190 | } | ||||
| 191 | } | ||||
| 192 | } | ||||
| 193 | |||||
| 194 | 1 | 3µs | 1 | 787µs | $meta = $metaclass->initialize($class); # spent 787µs making 1 call to Moose::Meta::Class::initialize |
| 195 | } | ||||
| 196 | |||||
| 197 | 1 | 9µs | 1 | 2µs | if ( $class->can('meta') ) { # spent 2µs making 1 call to UNIVERSAL::can |
| 198 | # check 'meta' method | ||||
| 199 | |||||
| 200 | # it may be inherited | ||||
| 201 | |||||
| 202 | # NOTE: | ||||
| 203 | # this is the case where the metaclass pragma | ||||
| 204 | # was used before the 'use Moose' statement to | ||||
| 205 | # override a specific class | ||||
| 206 | my $method_meta = $class->meta; | ||||
| 207 | |||||
| 208 | ( blessed($method_meta) && $method_meta->isa('Moose::Meta::Class') ) | ||||
| 209 | || Moose->throw_error("$class already has a &meta function, but it does not return a Moose::Meta::Class ($method_meta)"); | ||||
| 210 | |||||
| 211 | $meta = $method_meta; | ||||
| 212 | } | ||||
| 213 | |||||
| 214 | 1 | 12µs | 2 | 63µs | unless ( $meta->has_method("meta") ) { # don't overwrite # spent 34µs making 1 call to Class::MOP::Mixin::HasMethods::has_method
# spent 30µs making 1 call to Class::MOP::Mixin::HasMethods::add_method |
| 215 | # also check for inherited non moose 'meta' method? | ||||
| 216 | # FIXME also skip this if the user requested by passing an option | ||||
| 217 | $meta->add_method( | ||||
| 218 | 'meta' => sub { | ||||
| 219 | # re-initialize so it inherits properly | ||||
| 220 | 1 | 6µs | 1 | 5µs | $metaclass->initialize( ref($_[0]) || $_[0] ); # spent 5µs making 1 call to Moose::Meta::Class::initialize |
| 221 | } | ||||
| 222 | ); | ||||
| 223 | } | ||||
| 224 | |||||
| 225 | # make sure they inherit from Moose::Object | ||||
| 226 | 1 | 3µs | 2 | 273µs | $meta->superclasses($base_class) # spent 273µs making 2 calls to Moose::Meta::Class::superclasses, avg 136µs/call |
| 227 | unless $meta->superclasses(); | ||||
| 228 | |||||
| 229 | 1 | 5µs | return $meta; | ||
| 230 | } | ||||
| 231 | |||||
| 232 | # This may be used in some older MooseX extensions. | ||||
| 233 | sub _get_caller { | ||||
| 234 | goto &Moose::Exporter::_get_caller; | ||||
| 235 | } | ||||
| 236 | |||||
| 237 | ## make 'em all immutable | ||||
| 238 | |||||
| 239 | 22 | 16µs | 22 | 12µs | $_->make_immutable( # spent 12µs making 22 calls to Class::MOP::Class::is_mutable, avg 564ns/call |
| 240 | inline_constructor => 1, | ||||
| 241 | constructor_name => "_new", | ||||
| 242 | # these are Class::MOP accessors, so they need inlining | ||||
| 243 | inline_accessors => 1 | ||||
| 244 | 23 | 137µs | 44 | 37.3ms | ) for grep { $_->is_mutable } # spent 36.9ms making 22 calls to Class::MOP::Class::make_immutable, avg 1.68ms/call
# spent 309µs making 10 calls to Class::MOP::Object::meta, avg 31µs/call
# spent 21µs making 2 calls to Moose::Meta::Role::Method::Required::meta, avg 10µs/call
# spent 13µs making 1 call to Moose::Meta::TypeCoercion::meta
# spent 13µs making 1 call to Moose::Meta::Role::meta
# spent 12µs making 1 call to Moose::Meta::TypeCoercion::Union::meta
# spent 11µs making 1 call to Class::MOP::Mixin::meta
# spent 11µs making 1 call to Moose::Meta::Role::Application::ToRole::meta
# spent 11µs making 1 call to Moose::Meta::Role::Composite::meta
# spent 11µs making 1 call to Moose::Meta::Role::Application::RoleSummation::meta
# spent 10µs making 1 call to Moose::Meta::Role::Application::meta
# spent 10µs making 1 call to Moose::Meta::Role::Application::ToClass::meta
# spent 10µs making 1 call to Moose::Meta::Role::Application::ToInstance::meta |
| 245 | map { $_->meta } | ||||
| 246 | qw( | ||||
| 247 | Moose::Meta::Attribute | ||||
| 248 | Moose::Meta::Class | ||||
| 249 | Moose::Meta::Instance | ||||
| 250 | |||||
| 251 | Moose::Meta::TypeCoercion | ||||
| 252 | Moose::Meta::TypeCoercion::Union | ||||
| 253 | |||||
| 254 | Moose::Meta::Method | ||||
| 255 | Moose::Meta::Method::Accessor | ||||
| 256 | Moose::Meta::Method::Constructor | ||||
| 257 | Moose::Meta::Method::Destructor | ||||
| 258 | Moose::Meta::Method::Overridden | ||||
| 259 | Moose::Meta::Method::Augmented | ||||
| 260 | |||||
| 261 | Moose::Meta::Role | ||||
| 262 | Moose::Meta::Role::Attribute | ||||
| 263 | Moose::Meta::Role::Method | ||||
| 264 | Moose::Meta::Role::Method::Required | ||||
| 265 | Moose::Meta::Role::Method::Conflicting | ||||
| 266 | |||||
| 267 | Moose::Meta::Role::Composite | ||||
| 268 | |||||
| 269 | Moose::Meta::Role::Application | ||||
| 270 | Moose::Meta::Role::Application::RoleSummation | ||||
| 271 | Moose::Meta::Role::Application::ToClass | ||||
| 272 | Moose::Meta::Role::Application::ToRole | ||||
| 273 | Moose::Meta::Role::Application::ToInstance | ||||
| 274 | 1 | 0s | ); | ||
| 275 | |||||
| 276 | 1 | 7µs | 2 | 4.89ms | Moose::Meta::Mixin::AttributeCore->meta->make_immutable( # spent 4.86ms making 1 call to Class::MOP::Class::make_immutable
# spent 23µs making 1 call to Class::MOP::Mixin::meta |
| 277 | inline_constructor => 0, | ||||
| 278 | constructor_name => undef, | ||||
| 279 | ); | ||||
| 280 | |||||
| 281 | 1 | 36µs | 1; | ||
| 282 | |||||
| 283 | __END__ | ||||
| 284 | |||||
| 285 | =pod | ||||
| 286 | |||||
| 287 | =head1 NAME | ||||
| 288 | |||||
| 289 | Moose - A postmodern object system for Perl 5 | ||||
| 290 | |||||
| 291 | =head1 SYNOPSIS | ||||
| 292 | |||||
| 293 | package Point; | ||||
| 294 | use Moose; # automatically turns on strict and warnings | ||||
| 295 | |||||
| 296 | has 'x' => (is => 'rw', isa => 'Int'); | ||||
| 297 | has 'y' => (is => 'rw', isa => 'Int'); | ||||
| 298 | |||||
| 299 | sub clear { | ||||
| 300 | my $self = shift; | ||||
| 301 | $self->x(0); | ||||
| 302 | $self->y(0); | ||||
| 303 | } | ||||
| 304 | |||||
| 305 | package Point3D; | ||||
| 306 | use Moose; | ||||
| 307 | |||||
| 308 | extends 'Point'; | ||||
| 309 | |||||
| 310 | has 'z' => (is => 'rw', isa => 'Int'); | ||||
| 311 | |||||
| 312 | after 'clear' => sub { | ||||
| 313 | my $self = shift; | ||||
| 314 | $self->z(0); | ||||
| 315 | }; | ||||
| 316 | |||||
| 317 | =head1 DESCRIPTION | ||||
| 318 | |||||
| 319 | Moose is an extension of the Perl 5 object system. | ||||
| 320 | |||||
| 321 | The main goal of Moose is to make Perl 5 Object Oriented programming | ||||
| 322 | easier, more consistent and less tedious. With Moose you can to think | ||||
| 323 | more about what you want to do and less about the mechanics of OOP. | ||||
| 324 | |||||
| 325 | Additionally, Moose is built on top of L<Class::MOP>, which is a | ||||
| 326 | metaclass system for Perl 5. This means that Moose not only makes | ||||
| 327 | building normal Perl 5 objects better, but it provides the power of | ||||
| 328 | metaclass programming as well. | ||||
| 329 | |||||
| 330 | =head2 New to Moose? | ||||
| 331 | |||||
| 332 | If you're new to Moose, the best place to start is the | ||||
| 333 | L<Moose::Manual> docs, followed by the L<Moose::Cookbook>. The intro | ||||
| 334 | will show you what Moose is, and how it makes Perl 5 OO better. | ||||
| 335 | |||||
| 336 | The cookbook recipes on Moose basics will get you up to speed with | ||||
| 337 | many of Moose's features quickly. Once you have an idea of what Moose | ||||
| 338 | can do, you can use the API documentation to get more detail on | ||||
| 339 | features which interest you. | ||||
| 340 | |||||
| 341 | =head2 Moose Extensions | ||||
| 342 | |||||
| 343 | The C<MooseX::> namespace is the official place to find Moose extensions. | ||||
| 344 | These extensions can be found on the CPAN. The easiest way to find them | ||||
| 345 | is to search for them (L<http://search.cpan.org/search?query=MooseX::>), | ||||
| 346 | or to examine L<Task::Moose> which aims to keep an up-to-date, easily | ||||
| 347 | installable list of Moose extensions. | ||||
| 348 | |||||
| 349 | =head1 TRANSLATIONS | ||||
| 350 | |||||
| 351 | Much of the Moose documentation has been translated into other languages. | ||||
| 352 | |||||
| 353 | =over 4 | ||||
| 354 | |||||
| 355 | =item Japanese | ||||
| 356 | |||||
| 357 | Japanese docs can be found at L<http://perldoc.perlassociation.org/pod/Moose-Doc-JA/index.html>. The source POD files can be found in GitHub: L<http://github.com/jpa/Moose-Doc-JA> | ||||
| 358 | |||||
| 359 | =back | ||||
| 360 | |||||
| 361 | =head1 BUILDING CLASSES WITH MOOSE | ||||
| 362 | |||||
| 363 | Moose makes every attempt to provide as much convenience as possible during | ||||
| 364 | class construction/definition, but still stay out of your way if you want it | ||||
| 365 | to. Here are a few items to note when building classes with Moose. | ||||
| 366 | |||||
| 367 | Unless specified with C<extends>, any class which uses Moose will | ||||
| 368 | inherit from L<Moose::Object>. | ||||
| 369 | |||||
| 370 | Moose will also manage all attributes (including inherited ones) that are | ||||
| 371 | defined with C<has>. And (assuming you call C<new>, which is inherited from | ||||
| 372 | L<Moose::Object>) this includes properly initializing all instance slots, | ||||
| 373 | setting defaults where appropriate, and performing any type constraint checking | ||||
| 374 | or coercion. | ||||
| 375 | |||||
| 376 | =head1 PROVIDED METHODS | ||||
| 377 | |||||
| 378 | Moose provides a number of methods to all your classes, mostly through the | ||||
| 379 | inheritance of L<Moose::Object>. There is however, one exception. | ||||
| 380 | |||||
| 381 | =over 4 | ||||
| 382 | |||||
| 383 | =item B<meta> | ||||
| 384 | |||||
| 385 | This is a method which provides access to the current class's metaclass. | ||||
| 386 | |||||
| 387 | =back | ||||
| 388 | |||||
| 389 | =head1 EXPORTED FUNCTIONS | ||||
| 390 | |||||
| 391 | Moose will export a number of functions into the class's namespace which | ||||
| 392 | may then be used to set up the class. These functions all work directly | ||||
| 393 | on the current class. | ||||
| 394 | |||||
| 395 | =over 4 | ||||
| 396 | |||||
| 397 | =item B<extends (@superclasses)> | ||||
| 398 | |||||
| 399 | This function will set the superclass(es) for the current class. | ||||
| 400 | |||||
| 401 | This approach is recommended instead of C<use base>, because C<use base> | ||||
| 402 | actually C<push>es onto the class's C<@ISA>, whereas C<extends> will | ||||
| 403 | replace it. This is important to ensure that classes which do not have | ||||
| 404 | superclasses still properly inherit from L<Moose::Object>. | ||||
| 405 | |||||
| 406 | =item B<with (@roles)> | ||||
| 407 | |||||
| 408 | This will apply a given set of C<@roles> to the local class. | ||||
| 409 | |||||
| 410 | =item B<has $name|@$names =E<gt> %options> | ||||
| 411 | |||||
| 412 | This will install an attribute of a given C<$name> into the current class. If | ||||
| 413 | the first parameter is an array reference, it will create an attribute for | ||||
| 414 | every C<$name> in the list. The C<%options> are the same as those provided by | ||||
| 415 | L<Class::MOP::Attribute>, in addition to the list below which are provided by | ||||
| 416 | Moose (L<Moose::Meta::Attribute> to be more specific): | ||||
| 417 | |||||
| 418 | =over 4 | ||||
| 419 | |||||
| 420 | =item I<is =E<gt> 'rw'|'ro'> | ||||
| 421 | |||||
| 422 | The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read | ||||
| 423 | only). These will create either a read/write accessor or a read-only | ||||
| 424 | accessor respectively, using the same name as the C<$name> of the attribute. | ||||
| 425 | |||||
| 426 | If you need more control over how your accessors are named, you can | ||||
| 427 | use the L<reader|Class::MOP::Attribute/reader>, | ||||
| 428 | L<writer|Class::MOP::Attribute/writer> and | ||||
| 429 | L<accessor|Class::MOP::Attribute/accessor> options inherited from | ||||
| 430 | L<Class::MOP::Attribute>, however if you use those, you won't need the | ||||
| 431 | I<is> option. | ||||
| 432 | |||||
| 433 | =item I<isa =E<gt> $type_name> | ||||
| 434 | |||||
| 435 | The I<isa> option uses Moose's type constraint facilities to set up runtime | ||||
| 436 | type checking for this attribute. Moose will perform the checks during class | ||||
| 437 | construction, and within any accessors. The C<$type_name> argument must be a | ||||
| 438 | string. The string may be either a class name or a type defined using | ||||
| 439 | Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints> | ||||
| 440 | for information on how to define a new type, and how to retrieve type meta-data). | ||||
| 441 | |||||
| 442 | =item I<coerce =E<gt> (1|0)> | ||||
| 443 | |||||
| 444 | This will attempt to use coercion with the supplied type constraint to change | ||||
| 445 | the value passed into any accessors or constructors. You B<must> have supplied | ||||
| 446 | a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5> | ||||
| 447 | for an example. | ||||
| 448 | |||||
| 449 | =item I<does =E<gt> $role_name> | ||||
| 450 | |||||
| 451 | This will accept the name of a role which the value stored in this attribute | ||||
| 452 | is expected to have consumed. | ||||
| 453 | |||||
| 454 | =item I<required =E<gt> (1|0)> | ||||
| 455 | |||||
| 456 | This marks the attribute as being required. This means a value must be | ||||
| 457 | supplied during class construction, I<or> the attribute must be lazy | ||||
| 458 | and have either a default or a builder. Note that c<required> does not | ||||
| 459 | say anything about the attribute's value, which can be C<undef>. | ||||
| 460 | |||||
| 461 | =item I<weak_ref =E<gt> (1|0)> | ||||
| 462 | |||||
| 463 | This will tell the class to store the value of this attribute as a weakened | ||||
| 464 | reference. If an attribute is a weakened reference, it B<cannot> also be | ||||
| 465 | coerced. | ||||
| 466 | |||||
| 467 | =item I<lazy =E<gt> (1|0)> | ||||
| 468 | |||||
| 469 | This will tell the class to not create this slot until absolutely necessary. | ||||
| 470 | If an attribute is marked as lazy it B<must> have a default supplied. | ||||
| 471 | |||||
| 472 | =item I<auto_deref =E<gt> (1|0)> | ||||
| 473 | |||||
| 474 | This tells the accessor to automatically dereference the value of this | ||||
| 475 | attribute when called in list context. The accessor will still return a | ||||
| 476 | reference when called in scalar context. If this behavior isn't desirable, | ||||
| 477 | L<Moose::Meta::Attribute::Native::Trait::Array/elements> or | ||||
| 478 | L<Moose::Meta::Attribute::Native::Trait::Hash/elements> may be a better | ||||
| 479 | choice. The I<auto_deref> option is only legal if your I<isa> option is | ||||
| 480 | either C<ArrayRef> or C<HashRef>. | ||||
| 481 | |||||
| 482 | =item I<trigger =E<gt> $code> | ||||
| 483 | |||||
| 484 | The I<trigger> option is a CODE reference which will be called after | ||||
| 485 | the value of the attribute is set. The CODE ref will be passed the | ||||
| 486 | instance itself and the updated value. If the attribute already had a | ||||
| 487 | value, this will be passed as the third value to the trigger. | ||||
| 488 | |||||
| 489 | You B<can> have a trigger on a read-only attribute. | ||||
| 490 | |||||
| 491 | B<NOTE:> Triggers will only fire when you B<assign> to the attribute, | ||||
| 492 | either in the constructor, or using the writer. Default and built values will | ||||
| 493 | B<not> cause the trigger to be fired. | ||||
| 494 | |||||
| 495 | =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | DUCKTYPE | CODE> | ||||
| 496 | |||||
| 497 | The I<handles> option provides Moose classes with automated delegation features. | ||||
| 498 | This is a pretty complex and powerful option. It accepts many different option | ||||
| 499 | formats, each with its own benefits and drawbacks. | ||||
| 500 | |||||
| 501 | B<NOTE:> The class being delegated to does not need to be a Moose based class, | ||||
| 502 | which is why this feature is especially useful when wrapping non-Moose classes. | ||||
| 503 | |||||
| 504 | All I<handles> option formats share the following traits: | ||||
| 505 | |||||
| 506 | You cannot override a locally defined method with a delegated method; an | ||||
| 507 | exception will be thrown if you try. That is to say, if you define C<foo> in | ||||
| 508 | your class, you cannot override it with a delegated C<foo>. This is almost never | ||||
| 509 | something you would want to do, and if it is, you should do it by hand and not | ||||
| 510 | use Moose. | ||||
| 511 | |||||
| 512 | You cannot override any of the methods found in Moose::Object, or the C<BUILD> | ||||
| 513 | and C<DEMOLISH> methods. These will not throw an exception, but will silently | ||||
| 514 | move on to the next method in the list. My reasoning for this is that you would | ||||
| 515 | almost never want to do this, since it usually breaks your class. As with | ||||
| 516 | overriding locally defined methods, if you do want to do this, you should do it | ||||
| 517 | manually, not with Moose. | ||||
| 518 | |||||
| 519 | You do not I<need> to have a reader (or accessor) for the attribute in order | ||||
| 520 | to delegate to it. Moose will create a means of accessing the value for you, | ||||
| 521 | however this will be several times B<less> efficient then if you had given | ||||
| 522 | the attribute a reader (or accessor) to use. | ||||
| 523 | |||||
| 524 | Below is the documentation for each option format: | ||||
| 525 | |||||
| 526 | =over 4 | ||||
| 527 | |||||
| 528 | =item C<ARRAY> | ||||
| 529 | |||||
| 530 | This is the most common usage for I<handles>. You basically pass a list of | ||||
| 531 | method names to be delegated, and Moose will install a delegation method | ||||
| 532 | for each one. | ||||
| 533 | |||||
| 534 | =item C<HASH> | ||||
| 535 | |||||
| 536 | This is the second most common usage for I<handles>. Instead of a list of | ||||
| 537 | method names, you pass a HASH ref where each key is the method name you | ||||
| 538 | want installed locally, and its value is the name of the original method | ||||
| 539 | in the class being delegated to. | ||||
| 540 | |||||
| 541 | This can be very useful for recursive classes like trees. Here is a | ||||
| 542 | quick example (soon to be expanded into a Moose::Cookbook recipe): | ||||
| 543 | |||||
| 544 | package Tree; | ||||
| 545 | use Moose; | ||||
| 546 | |||||
| 547 | has 'node' => (is => 'rw', isa => 'Any'); | ||||
| 548 | |||||
| 549 | has 'children' => ( | ||||
| 550 | is => 'ro', | ||||
| 551 | isa => 'ArrayRef', | ||||
| 552 | default => sub { [] } | ||||
| 553 | ); | ||||
| 554 | |||||
| 555 | has 'parent' => ( | ||||
| 556 | is => 'rw', | ||||
| 557 | isa => 'Tree', | ||||
| 558 | weak_ref => 1, | ||||
| 559 | handles => { | ||||
| 560 | parent_node => 'node', | ||||
| 561 | siblings => 'children', | ||||
| 562 | } | ||||
| 563 | ); | ||||
| 564 | |||||
| 565 | In this example, the Tree package gets C<parent_node> and C<siblings> methods, | ||||
| 566 | which delegate to the C<node> and C<children> methods (respectively) of the Tree | ||||
| 567 | instance stored in the C<parent> slot. | ||||
| 568 | |||||
| 569 | You may also use an array reference to curry arguments to the original method. | ||||
| 570 | |||||
| 571 | has 'thing' => ( | ||||
| 572 | ... | ||||
| 573 | handles => { set_foo => [ set => 'foo' ] }, | ||||
| 574 | ); | ||||
| 575 | |||||
| 576 | # $self->set_foo(...) calls $self->thing->set('foo', ...) | ||||
| 577 | |||||
| 578 | The first element of the array reference is the original method name, and the | ||||
| 579 | rest is a list of curried arguments. | ||||
| 580 | |||||
| 581 | =item C<REGEXP> | ||||
| 582 | |||||
| 583 | The regexp option works very similar to the ARRAY option, except that it builds | ||||
| 584 | the list of methods for you. It starts by collecting all possible methods of the | ||||
| 585 | class being delegated to, then filters that list using the regexp supplied here. | ||||
| 586 | |||||
| 587 | B<NOTE:> An I<isa> option is required when using the regexp option format. This | ||||
| 588 | is so that we can determine (at compile time) the method list from the class. | ||||
| 589 | Without an I<isa> this is just not possible. | ||||
| 590 | |||||
| 591 | =item C<ROLE> | ||||
| 592 | |||||
| 593 | With the role option, you specify the name of a role whose "interface" then | ||||
| 594 | becomes the list of methods to handle. The "interface" can be defined as; the | ||||
| 595 | methods of the role and any required methods of the role. It should be noted | ||||
| 596 | that this does B<not> include any method modifiers or generated attribute | ||||
| 597 | methods (which is consistent with role composition). | ||||
| 598 | |||||
| 599 | =item C<DUCKTYPE> | ||||
| 600 | |||||
| 601 | With the duck type option, you pass a duck type object whose "interface" then | ||||
| 602 | becomes the list of methods to handle. The "interface" can be defined as; the | ||||
| 603 | list of methods passed to C<duck_type> to create a duck type object. For more | ||||
| 604 | information on C<duck_type> please check | ||||
| 605 | L<Moose::Util::TypeConstraints>. | ||||
| 606 | |||||
| 607 | =item C<CODE> | ||||
| 608 | |||||
| 609 | This is the option to use when you really want to do something funky. You should | ||||
| 610 | only use it if you really know what you are doing, as it involves manual | ||||
| 611 | metaclass twiddling. | ||||
| 612 | |||||
| 613 | This takes a code reference, which should expect two arguments. The first is the | ||||
| 614 | attribute meta-object this I<handles> is attached to. The second is the | ||||
| 615 | metaclass of the class being delegated to. It expects you to return a hash (not | ||||
| 616 | a HASH ref) of the methods you want mapped. | ||||
| 617 | |||||
| 618 | =back | ||||
| 619 | |||||
| 620 | =item I<metaclass =E<gt> $metaclass_name> | ||||
| 621 | |||||
| 622 | This tells the class to use a custom attribute metaclass for this particular | ||||
| 623 | attribute. Custom attribute metaclasses are useful for extending the | ||||
| 624 | capabilities of the I<has> keyword: they are the simplest way to extend the MOP, | ||||
| 625 | but they are still a fairly advanced topic and too much to cover here, see | ||||
| 626 | L<Moose::Cookbook::Meta::Recipe1> for more information. | ||||
| 627 | |||||
| 628 | See L<Metaclass and Trait Name Resolution> for details on how a metaclass name | ||||
| 629 | is resolved to a class name. | ||||
| 630 | |||||
| 631 | =item I<traits =E<gt> [ @role_names ]> | ||||
| 632 | |||||
| 633 | This tells Moose to take the list of C<@role_names> and apply them to the | ||||
| 634 | attribute meta-object. This is very similar to the I<metaclass> option, but | ||||
| 635 | allows you to use more than one extension at a time. | ||||
| 636 | |||||
| 637 | See L<Metaclass and Trait Name Resolution> for details on how a trait name is | ||||
| 638 | resolved to a role name. | ||||
| 639 | |||||
| 640 | Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait | ||||
| 641 | example. | ||||
| 642 | |||||
| 643 | =item I<builder> => Str | ||||
| 644 | |||||
| 645 | The value of this key is the name of the method that will be called to | ||||
| 646 | obtain the value used to initialize the attribute. See the L<builder | ||||
| 647 | option docs in Class::MOP::Attribute|Class::MOP::Attribute/builder> | ||||
| 648 | and/or L<Moose::Cookbook::Basics::Recipe8> for more information. | ||||
| 649 | |||||
| 650 | =item I<default> => SCALAR | CODE | ||||
| 651 | |||||
| 652 | The value of this key is the default value which will initialize the attribute. | ||||
| 653 | |||||
| 654 | NOTE: If the value is a simple scalar (string or number), then it can | ||||
| 655 | be just passed as is. However, if you wish to initialize it with a | ||||
| 656 | HASH or ARRAY ref, then you need to wrap that inside a CODE reference. | ||||
| 657 | See the L<default option docs in | ||||
| 658 | Class::MOP::Attribute|Class::MOP::Attribute/default> for more | ||||
| 659 | information. | ||||
| 660 | |||||
| 661 | =item I<clearer> => Str | ||||
| 662 | |||||
| 663 | Creates a method allowing you to clear the value, see the L<clearer option | ||||
| 664 | docs in Class::MOP::Attribute|Class::MOP::Attribute/clearer> for more | ||||
| 665 | information. | ||||
| 666 | |||||
| 667 | =item I<predicate> => Str | ||||
| 668 | |||||
| 669 | Creates a method to perform a basic test to see if a value has been set in the | ||||
| 670 | attribute, see the L<predicate option docs in | ||||
| 671 | Class::MOP::Attribute|Class::MOP::Attribute/predicate> for more information. | ||||
| 672 | |||||
| 673 | =item I<lazy_build> => (0|1) | ||||
| 674 | |||||
| 675 | Automatically define lazy => 1 as well as builder => "_build_$attr", clearer => | ||||
| 676 | "clear_$attr', predicate => 'has_$attr' unless they are already defined. | ||||
| 677 | |||||
| 678 | =item I<initializer> => Str | ||||
| 679 | |||||
| 680 | This may be a method name (referring to a method on the class with | ||||
| 681 | this attribute) or a CODE ref. The initializer is used to set the | ||||
| 682 | attribute value on an instance when the attribute is set during | ||||
| 683 | instance initialization (but not when the value is being assigned | ||||
| 684 | to). See the L<initializer option docs in | ||||
| 685 | Class::MOP::Attribute|Class::MOP::Attribute/initializer> for more | ||||
| 686 | information. | ||||
| 687 | |||||
| 688 | =item I<documentation> => $string | ||||
| 689 | |||||
| 690 | An arbitrary string that can be retrieved later by calling C<< | ||||
| 691 | $attr->documentation >>. | ||||
| 692 | |||||
| 693 | |||||
| 694 | |||||
| 695 | =back | ||||
| 696 | |||||
| 697 | =item B<has +$name =E<gt> %options> | ||||
| 698 | |||||
| 699 | This is variation on the normal attribute creator C<has> which allows you to | ||||
| 700 | clone and extend an attribute from a superclass or from a role. Here is an | ||||
| 701 | example of the superclass usage: | ||||
| 702 | |||||
| 703 | package Foo; | ||||
| 704 | use Moose; | ||||
| 705 | |||||
| 706 | has 'message' => ( | ||||
| 707 | is => 'rw', | ||||
| 708 | isa => 'Str', | ||||
| 709 | default => 'Hello, I am a Foo' | ||||
| 710 | ); | ||||
| 711 | |||||
| 712 | package My::Foo; | ||||
| 713 | use Moose; | ||||
| 714 | |||||
| 715 | extends 'Foo'; | ||||
| 716 | |||||
| 717 | has '+message' => (default => 'Hello I am My::Foo'); | ||||
| 718 | |||||
| 719 | What is happening here is that B<My::Foo> is cloning the C<message> attribute | ||||
| 720 | from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt> | ||||
| 721 | 'Str'> characteristics, but changing the value in C<default>. | ||||
| 722 | |||||
| 723 | Here is another example, but within the context of a role: | ||||
| 724 | |||||
| 725 | package Foo::Role; | ||||
| 726 | use Moose::Role; | ||||
| 727 | |||||
| 728 | has 'message' => ( | ||||
| 729 | is => 'rw', | ||||
| 730 | isa => 'Str', | ||||
| 731 | default => 'Hello, I am a Foo' | ||||
| 732 | ); | ||||
| 733 | |||||
| 734 | package My::Foo; | ||||
| 735 | use Moose; | ||||
| 736 | |||||
| 737 | with 'Foo::Role'; | ||||
| 738 | |||||
| 739 | has '+message' => (default => 'Hello I am My::Foo'); | ||||
| 740 | |||||
| 741 | In this case, we are basically taking the attribute which the role supplied | ||||
| 742 | and altering it within the bounds of this feature. | ||||
| 743 | |||||
| 744 | Note that you can only extend an attribute from either a superclass or a role, | ||||
| 745 | you cannot extend an attribute in a role that composes over an attribute from | ||||
| 746 | another role. | ||||
| 747 | |||||
| 748 | Aside from where the attributes come from (one from superclass, the other | ||||
| 749 | from a role), this feature works exactly the same. This feature is restricted | ||||
| 750 | somewhat, so as to try and force at least I<some> sanity into it. You are only | ||||
| 751 | allowed to change the following attributes: | ||||
| 752 | |||||
| 753 | =over 4 | ||||
| 754 | |||||
| 755 | =item I<default> | ||||
| 756 | |||||
| 757 | Change the default value of an attribute. | ||||
| 758 | |||||
| 759 | =item I<coerce> | ||||
| 760 | |||||
| 761 | Change whether the attribute attempts to coerce a value passed to it. | ||||
| 762 | |||||
| 763 | =item I<required> | ||||
| 764 | |||||
| 765 | Change if the attribute is required to have a value. | ||||
| 766 | |||||
| 767 | =item I<documentation> | ||||
| 768 | |||||
| 769 | Change the documentation string associated with the attribute. | ||||
| 770 | |||||
| 771 | =item I<lazy> | ||||
| 772 | |||||
| 773 | Change if the attribute lazily initializes the slot. | ||||
| 774 | |||||
| 775 | =item I<isa> | ||||
| 776 | |||||
| 777 | You I<are> allowed to change the type without restriction. | ||||
| 778 | |||||
| 779 | It is recommended that you use this freedom with caution. We used to | ||||
| 780 | only allow for extension only if the type was a subtype of the parent's | ||||
| 781 | type, but we felt that was too restrictive and is better left as a | ||||
| 782 | policy decision. | ||||
| 783 | |||||
| 784 | =item I<handles> | ||||
| 785 | |||||
| 786 | You are allowed to B<add> a new C<handles> definition, but you are B<not> | ||||
| 787 | allowed to I<change> one. | ||||
| 788 | |||||
| 789 | =item I<builder> | ||||
| 790 | |||||
| 791 | You are allowed to B<add> a new C<builder> definition, but you are B<not> | ||||
| 792 | allowed to I<change> one. | ||||
| 793 | |||||
| 794 | =item I<metaclass> | ||||
| 795 | |||||
| 796 | You are allowed to B<add> a new C<metaclass> definition, but you are | ||||
| 797 | B<not> allowed to I<change> one. | ||||
| 798 | |||||
| 799 | =item I<traits> | ||||
| 800 | |||||
| 801 | You are allowed to B<add> additional traits to the C<traits> definition. | ||||
| 802 | These traits will be composed into the attribute, but preexisting traits | ||||
| 803 | B<are not> overridden, or removed. | ||||
| 804 | |||||
| 805 | =back | ||||
| 806 | |||||
| 807 | =item B<before $name|@names =E<gt> sub { ... }> | ||||
| 808 | |||||
| 809 | =item B<after $name|@names =E<gt> sub { ... }> | ||||
| 810 | |||||
| 811 | =item B<around $name|@names =E<gt> sub { ... }> | ||||
| 812 | |||||
| 813 | These three items are syntactic sugar for the before, after, and around method | ||||
| 814 | modifier features that L<Class::MOP> provides. More information on these may be | ||||
| 815 | found in L<Moose::Manual::MethodModifiers> and the | ||||
| 816 | L<Class::MOP::Class documentation|Class::MOP::Class/"Method Modifiers">. | ||||
| 817 | |||||
| 818 | =item B<super> | ||||
| 819 | |||||
| 820 | The keyword C<super> is a no-op when called outside of an C<override> method. In | ||||
| 821 | the context of an C<override> method, it will call the next most appropriate | ||||
| 822 | superclass method with the same arguments as the original method. | ||||
| 823 | |||||
| 824 | =item B<override ($name, &sub)> | ||||
| 825 | |||||
| 826 | An C<override> method is a way of explicitly saying "I am overriding this | ||||
| 827 | method from my superclass". You can call C<super> within this method, and | ||||
| 828 | it will work as expected. The same thing I<can> be accomplished with a normal | ||||
| 829 | method call and the C<SUPER::> pseudo-package; it is really your choice. | ||||
| 830 | |||||
| 831 | =item B<inner> | ||||
| 832 | |||||
| 833 | The keyword C<inner>, much like C<super>, is a no-op outside of the context of | ||||
| 834 | an C<augment> method. You can think of C<inner> as being the inverse of | ||||
| 835 | C<super>; the details of how C<inner> and C<augment> work is best described in | ||||
| 836 | the L<Moose::Cookbook::Basics::Recipe6>. | ||||
| 837 | |||||
| 838 | =item B<augment ($name, &sub)> | ||||
| 839 | |||||
| 840 | An C<augment> method, is a way of explicitly saying "I am augmenting this | ||||
| 841 | method from my superclass". Once again, the details of how C<inner> and | ||||
| 842 | C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>. | ||||
| 843 | |||||
| 844 | =item B<confess> | ||||
| 845 | |||||
| 846 | This is the C<Carp::confess> function, and exported here because I use it | ||||
| 847 | all the time. | ||||
| 848 | |||||
| 849 | =item B<blessed> | ||||
| 850 | |||||
| 851 | This is the C<Scalar::Util::blessed> function, it is exported here because I | ||||
| 852 | use it all the time. It is highly recommended that this is used instead of | ||||
| 853 | C<ref> anywhere you need to test for an object's class name. | ||||
| 854 | |||||
| 855 | =back | ||||
| 856 | |||||
| 857 | =head1 METACLASS | ||||
| 858 | |||||
| 859 | When you use Moose, you can specify which metaclass to use: | ||||
| 860 | |||||
| 861 | use Moose -metaclass => 'My::Meta::Class'; | ||||
| 862 | |||||
| 863 | You can also specify traits which will be applied to your metaclass: | ||||
| 864 | |||||
| 865 | use Moose -traits => 'My::Trait'; | ||||
| 866 | |||||
| 867 | This is very similar to the attribute traits feature. When you do | ||||
| 868 | this, your class's C<meta> object will have the specified traits | ||||
| 869 | applied to it. See L<Metaclass and Trait Name Resolution> for more | ||||
| 870 | details. | ||||
| 871 | |||||
| 872 | =head2 Metaclass and Trait Name Resolution | ||||
| 873 | |||||
| 874 | By default, when given a trait name, Moose simply tries to load a | ||||
| 875 | class of the same name. If such a class does not exist, it then looks | ||||
| 876 | for for a class matching | ||||
| 877 | B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type> | ||||
| 878 | variable here will be one of B<Attribute> or B<Class>, depending on | ||||
| 879 | what the trait is being applied to. | ||||
| 880 | |||||
| 881 | If a class with this long name exists, Moose checks to see if it has | ||||
| 882 | the method C<register_implementation>. This method is expected to | ||||
| 883 | return the I<real> class name of the trait. If there is no | ||||
| 884 | C<register_implementation> method, it will fall back to using | ||||
| 885 | B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name. | ||||
| 886 | |||||
| 887 | The lookup method for metaclasses is the same, except that it looks | ||||
| 888 | for a class matching B<Moose::Meta::$type::Custom::$metaclass_name>. | ||||
| 889 | |||||
| 890 | If all this is confusing, take a look at | ||||
| 891 | L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an | ||||
| 892 | attribute trait. | ||||
| 893 | |||||
| 894 | =head1 UNIMPORTING FUNCTIONS | ||||
| 895 | |||||
| 896 | =head2 B<unimport> | ||||
| 897 | |||||
| 898 | Moose offers a way to remove the keywords it exports, through the C<unimport> | ||||
| 899 | method. You simply have to say C<no Moose> at the bottom of your code for this | ||||
| 900 | to work. Here is an example: | ||||
| 901 | |||||
| 902 | package Person; | ||||
| 903 | use Moose; | ||||
| 904 | |||||
| 905 | has 'first_name' => (is => 'rw', isa => 'Str'); | ||||
| 906 | has 'last_name' => (is => 'rw', isa => 'Str'); | ||||
| 907 | |||||
| 908 | sub full_name { | ||||
| 909 | my $self = shift; | ||||
| 910 | $self->first_name . ' ' . $self->last_name | ||||
| 911 | } | ||||
| 912 | |||||
| 913 | no Moose; # keywords are removed from the Person package | ||||
| 914 | |||||
| 915 | =head1 EXTENDING AND EMBEDDING MOOSE | ||||
| 916 | |||||
| 917 | To learn more about extending Moose, we recommend checking out the | ||||
| 918 | "Extending" recipes in the L<Moose::Cookbook>, starting with | ||||
| 919 | L<Moose::Cookbook::Extending::Recipe1>, which provides an overview of | ||||
| 920 | all the different ways you might extend Moose. | ||||
| 921 | |||||
| 922 | =head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >> | ||||
| 923 | |||||
| 924 | The C<init_meta> method sets up the metaclass object for the class | ||||
| 925 | specified by C<for_class>. This method injects a a C<meta> accessor | ||||
| 926 | into the class so you can get at this object. It also sets the class's | ||||
| 927 | superclass to C<base_class>, with L<Moose::Object> as the default. | ||||
| 928 | |||||
| 929 | C<init_meta> returns the metaclass object for C<$class>. | ||||
| 930 | |||||
| 931 | You can specify an alternate metaclass with the C<metaclass> option. | ||||
| 932 | |||||
| 933 | For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>. | ||||
| 934 | |||||
| 935 | This method used to be documented as a function which accepted | ||||
| 936 | positional parameters. This calling style will still work for | ||||
| 937 | backwards compatibility, but is deprecated. | ||||
| 938 | |||||
| 939 | =head2 B<import> | ||||
| 940 | |||||
| 941 | Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}> | ||||
| 942 | and C<{into_level =E<gt> 1}>. | ||||
| 943 | |||||
| 944 | B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter> | ||||
| 945 | instead, which lets you stack multiple C<Moose.pm>-alike modules | ||||
| 946 | sanely. It handles getting the exported functions into the right place | ||||
| 947 | for you. | ||||
| 948 | |||||
| 949 | =head2 B<throw_error> | ||||
| 950 | |||||
| 951 | An alias for C<confess>, used by internally by Moose. | ||||
| 952 | |||||
| 953 | =head1 METACLASS COMPATIBILITY AND MOOSE | ||||
| 954 | |||||
| 955 | Metaclass compatibility is a thorny subject. You should start by | ||||
| 956 | reading the "About Metaclass compatibility" section in the | ||||
| 957 | C<Class::MOP> docs. | ||||
| 958 | |||||
| 959 | Moose will attempt to resolve a few cases of metaclass incompatibility | ||||
| 960 | when you set the superclasses for a class, unlike C<Class::MOP>, which | ||||
| 961 | simply dies if the metaclasses are incompatible. | ||||
| 962 | |||||
| 963 | In actuality, Moose fixes incompatibility for I<all> of a class's | ||||
| 964 | metaclasses, not just the class metaclass. That includes the instance | ||||
| 965 | metaclass, attribute metaclass, as well as its constructor class and | ||||
| 966 | destructor class. However, for simplicity this discussion will just | ||||
| 967 | refer to "metaclass", meaning the class metaclass, most of the time. | ||||
| 968 | |||||
| 969 | Moose has two algorithms for fixing metaclass incompatibility. | ||||
| 970 | |||||
| 971 | The first algorithm is very simple. If all the metaclass for the | ||||
| 972 | parent is a I<subclass> of the child's metaclass, then we simply | ||||
| 973 | replace the child's metaclass with the parent's. | ||||
| 974 | |||||
| 975 | The second algorithm is more complicated. It tries to determine if the | ||||
| 976 | metaclasses only "differ by roles". This means that the parent and | ||||
| 977 | child's metaclass share a common ancestor in their respective | ||||
| 978 | hierarchies, and that the subclasses under the common ancestor are | ||||
| 979 | only different because of role applications. This case is actually | ||||
| 980 | fairly common when you mix and match various C<MooseX::*> modules, | ||||
| 981 | many of which apply roles to the metaclass. | ||||
| 982 | |||||
| 983 | If the parent and child do differ by roles, Moose replaces the | ||||
| 984 | metaclass in the child with a newly created metaclass. This metaclass | ||||
| 985 | is a subclass of the parent's metaclass, does all of the roles that | ||||
| 986 | the child's metaclass did before being replaced. Effectively, this | ||||
| 987 | means the new metaclass does all of the roles done by both the | ||||
| 988 | parent's and child's original metaclasses. | ||||
| 989 | |||||
| 990 | Ultimately, this is all transparent to you except in the case of an | ||||
| 991 | unresolvable conflict. | ||||
| 992 | |||||
| 993 | =head2 The MooseX:: namespace | ||||
| 994 | |||||
| 995 | Generally if you're writing an extension I<for> Moose itself you'll want | ||||
| 996 | to put your extension in the C<MooseX::> namespace. This namespace is | ||||
| 997 | specifically for extensions that make Moose better or different in some | ||||
| 998 | fundamental way. It is traditionally B<not> for a package that just happens | ||||
| 999 | to use Moose. This namespace follows from the examples of the C<LWPx::> | ||||
| 1000 | and C<DBIx::> namespaces that perform the same function for C<LWP> and C<DBI> | ||||
| 1001 | respectively. | ||||
| 1002 | |||||
| 1003 | =head1 CAVEATS | ||||
| 1004 | |||||
| 1005 | =over 4 | ||||
| 1006 | |||||
| 1007 | =item * | ||||
| 1008 | |||||
| 1009 | It should be noted that C<super> and C<inner> B<cannot> be used in the same | ||||
| 1010 | method. However, they may be combined within the same class hierarchy; see | ||||
| 1011 | F<t/014_override_augment_inner_super.t> for an example. | ||||
| 1012 | |||||
| 1013 | The reason for this is that C<super> is only valid within a method | ||||
| 1014 | with the C<override> modifier, and C<inner> will never be valid within an | ||||
| 1015 | C<override> method. In fact, C<augment> will skip over any C<override> methods | ||||
| 1016 | when searching for its appropriate C<inner>. | ||||
| 1017 | |||||
| 1018 | This might seem like a restriction, but I am of the opinion that keeping these | ||||
| 1019 | two features separate (yet interoperable) actually makes them easy to use, since | ||||
| 1020 | their behavior is then easier to predict. Time will tell whether I am right or | ||||
| 1021 | not (UPDATE: so far so good). | ||||
| 1022 | |||||
| 1023 | =back | ||||
| 1024 | |||||
| 1025 | =head1 GETTING HELP | ||||
| 1026 | |||||
| 1027 | We offer both a mailing list and a very active IRC channel. | ||||
| 1028 | |||||
| 1029 | The mailing list is L<moose@perl.org>. You must be subscribed to send | ||||
| 1030 | a message. To subscribe, send an empty message to | ||||
| 1031 | L<moose-subscribe@perl.org> | ||||
| 1032 | |||||
| 1033 | You can also visit us at C<#moose> on L<irc://irc.perl.org/#moose> | ||||
| 1034 | This channel is quite active, and questions at all levels (on Moose-related | ||||
| 1035 | topics ;) are welcome. | ||||
| 1036 | |||||
| 1037 | =head1 ACKNOWLEDGEMENTS | ||||
| 1038 | |||||
| 1039 | =over 4 | ||||
| 1040 | |||||
| 1041 | =item I blame Sam Vilain for introducing me to the insanity that is meta-models. | ||||
| 1042 | |||||
| 1043 | =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6. | ||||
| 1044 | |||||
| 1045 | =item Without Yuval "nothingmuch" Kogman this module would not be possible, | ||||
| 1046 | and it certainly wouldn't have this name ;P | ||||
| 1047 | |||||
| 1048 | =item The basis of the TypeContraints module was Rob Kinyon's idea | ||||
| 1049 | originally, I just ran with it. | ||||
| 1050 | |||||
| 1051 | =item Thanks to mst & chansen and the whole #moose posse for all the | ||||
| 1052 | early ideas/feature-requests/encouragement/bug-finding. | ||||
| 1053 | |||||
| 1054 | =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes. | ||||
| 1055 | |||||
| 1056 | =back | ||||
| 1057 | |||||
| 1058 | =head1 SEE ALSO | ||||
| 1059 | |||||
| 1060 | =over 4 | ||||
| 1061 | |||||
| 1062 | =item L<http://www.iinteractive.com/moose> | ||||
| 1063 | |||||
| 1064 | This is the official web home of Moose, it contains links to our public SVN repository | ||||
| 1065 | as well as links to a number of talks and articles on Moose and Moose related | ||||
| 1066 | technologies. | ||||
| 1067 | |||||
| 1068 | =item The Moose is flying, a tutorial by Randal Schwartz | ||||
| 1069 | |||||
| 1070 | Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html> | ||||
| 1071 | |||||
| 1072 | Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html> | ||||
| 1073 | |||||
| 1074 | =item Several Moose extension modules in the C<MooseX::> namespace. | ||||
| 1075 | |||||
| 1076 | See L<http://search.cpan.org/search?query=MooseX::> for extensions. | ||||
| 1077 | |||||
| 1078 | =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose> | ||||
| 1079 | |||||
| 1080 | =back | ||||
| 1081 | |||||
| 1082 | =head2 Books | ||||
| 1083 | |||||
| 1084 | =over 4 | ||||
| 1085 | |||||
| 1086 | =item The Art of the MetaObject Protocol | ||||
| 1087 | |||||
| 1088 | I mention this in the L<Class::MOP> docs too, this book was critical in | ||||
| 1089 | the development of both modules and is highly recommended. | ||||
| 1090 | |||||
| 1091 | =back | ||||
| 1092 | |||||
| 1093 | =head2 Papers | ||||
| 1094 | |||||
| 1095 | =over 4 | ||||
| 1096 | |||||
| 1097 | =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf> | ||||
| 1098 | |||||
| 1099 | This paper (suggested by lbr on #moose) was what lead to the implementation | ||||
| 1100 | of the C<super>/C<override> and C<inner>/C<augment> features. If you really | ||||
| 1101 | want to understand them, I suggest you read this. | ||||
| 1102 | |||||
| 1103 | =back | ||||
| 1104 | |||||
| 1105 | =head1 BUGS | ||||
| 1106 | |||||
| 1107 | All complex software has bugs lurking in it, and this module is no | ||||
| 1108 | exception. | ||||
| 1109 | |||||
| 1110 | Please report any bugs to C<bug-moose@rt.cpan.org>, or through the web | ||||
| 1111 | interface at L<http://rt.cpan.org>. | ||||
| 1112 | |||||
| 1113 | You can also discuss feature requests or possible bugs on the Moose mailing | ||||
| 1114 | list (moose@perl.org) or on IRC at L<irc://irc.perl.org/#moose>. | ||||
| 1115 | |||||
| 1116 | =head1 FEATURE REQUESTS | ||||
| 1117 | |||||
| 1118 | We are very strict about what features we add to the Moose core, especially | ||||
| 1119 | the user-visible features. Instead we have made sure that the underlying | ||||
| 1120 | meta-system of Moose is as extensible as possible so that you can add your | ||||
| 1121 | own features easily. | ||||
| 1122 | |||||
| 1123 | That said, occasionally there is a feature needed in the meta-system | ||||
| 1124 | to support your planned extension, in which case you should either | ||||
| 1125 | email the mailing list (moose@perl.org) or join us on IRC at | ||||
| 1126 | L<irc://irc.perl.org/#moose> to discuss. The | ||||
| 1127 | L<Moose::Manual::Contributing> has more detail about how and when you | ||||
| 1128 | can contribute. | ||||
| 1129 | |||||
| 1130 | =head1 AUTHOR | ||||
| 1131 | |||||
| 1132 | Moose is an open project, there are at this point dozens of people who have | ||||
| 1133 | contributed, and can contribute. If you have added anything to the Moose | ||||
| 1134 | project you have a commit bit on this file and can add your name to the list. | ||||
| 1135 | |||||
| 1136 | =head2 CABAL | ||||
| 1137 | |||||
| 1138 | However there are only a few people with the rights to release a new version | ||||
| 1139 | of Moose. The Moose Cabal are the people to go to with questions regarding | ||||
| 1140 | the wider purview of Moose, and help out maintaining not just the code | ||||
| 1141 | but the community as well. | ||||
| 1142 | |||||
| 1143 | Stevan (stevan) Little E<lt>stevan@iinteractive.comE<gt> | ||||
| 1144 | |||||
| 1145 | Jesse (doy) Luehrs E<lt>doy at tozt dot netE<gt> | ||||
| 1146 | |||||
| 1147 | Yuval (nothingmuch) Kogman | ||||
| 1148 | |||||
| 1149 | Shawn (sartak) Moore E<lt>sartak@bestpractical.comE<gt> | ||||
| 1150 | |||||
| 1151 | Hans Dieter (confound) Pearcey E<lt>hdp@pobox.comE<gt> | ||||
| 1152 | |||||
| 1153 | Chris (perigrin) Prather | ||||
| 1154 | |||||
| 1155 | Florian Ragwitz E<lt>rafl@debian.orgE<gt> | ||||
| 1156 | |||||
| 1157 | Dave (autarch) Rolsky E<lt>autarch@urth.orgE<gt> | ||||
| 1158 | |||||
| 1159 | =head2 OTHER CONTRIBUTORS | ||||
| 1160 | |||||
| 1161 | Aankhen | ||||
| 1162 | |||||
| 1163 | Adam (Alias) Kennedy | ||||
| 1164 | |||||
| 1165 | Anders (Debolaz) Nor Berle | ||||
| 1166 | |||||
| 1167 | Nathan (kolibrie) Gray | ||||
| 1168 | |||||
| 1169 | Christian (chansen) Hansen | ||||
| 1170 | |||||
| 1171 | Eric (ewilhelm) Wilhelm | ||||
| 1172 | |||||
| 1173 | Guillermo (groditi) Roditi | ||||
| 1174 | |||||
| 1175 | Jess (castaway) Robinson | ||||
| 1176 | |||||
| 1177 | Matt (mst) Trout | ||||
| 1178 | |||||
| 1179 | Robert (phaylon) Sedlacek | ||||
| 1180 | |||||
| 1181 | Robert (rlb3) Boone | ||||
| 1182 | |||||
| 1183 | Scott (konobi) McWhirter | ||||
| 1184 | |||||
| 1185 | Shlomi (rindolf) Fish | ||||
| 1186 | |||||
| 1187 | Wallace (wreis) Reis | ||||
| 1188 | |||||
| 1189 | Jonathan (jrockway) Rockway | ||||
| 1190 | |||||
| 1191 | Piotr (dexter) Roszatycki | ||||
| 1192 | |||||
| 1193 | Sam (mugwump) Vilain | ||||
| 1194 | |||||
| 1195 | Cory (gphat) Watson | ||||
| 1196 | |||||
| 1197 | Dylan Hardison (doc fixes) | ||||
| 1198 | |||||
| 1199 | ... and many other #moose folks | ||||
| 1200 | |||||
| 1201 | =head1 COPYRIGHT AND LICENSE | ||||
| 1202 | |||||
| 1203 | Copyright 2006-2010 by Infinity Interactive, Inc. | ||||
| 1204 | |||||
| 1205 | L<http://www.iinteractive.com> | ||||
| 1206 | |||||
| 1207 | This library is free software; you can redistribute it and/or modify | ||||
| 1208 | it under the same terms as Perl itself. | ||||
| 1209 | |||||
| 1210 | =cut | ||||
# spent 15µs within Moose::bootstrap which was called
# once (15µs+0s) by DynaLoader::bootstrap at line 227 of DynaLoader.pm |