← Index
NYTProf Performance Profile   « block view • line view • sub view »
For 01.HTTP.t
  Run on Tue May 4 15:25:55 2010
Reported on Tue May 4 15:26:11 2010

File /usr/local/lib/perl5/site_perl/5.10.1/darwin-2level/Moose.pm
Statements Executed 170
Statement Execution Time 4.92ms
Subroutines — ordered by exclusive time
Calls P F Exclusive
Time
Inclusive
Time
Subroutine
1113.49ms172msMoose::::BEGIN@14Moose::BEGIN@14
1112.68ms13.1msMoose::::BEGIN@26Moose::BEGIN@26
1112.64ms21.5msMoose::::BEGIN@18Moose::BEGIN@18
1111.42ms2.73msMoose::::BEGIN@11Moose::BEGIN@11
1111.39ms17.2msMoose::::BEGIN@19Moose::BEGIN@19
1111.37ms2.88msMoose::::BEGIN@24Moose::BEGIN@24
1111.36ms1.92msMoose::::BEGIN@29Moose::BEGIN@29
1111.27ms59.7msMoose::::BEGIN@20Moose::BEGIN@20
111947µs1.99msMoose::::BEGIN@30Moose::BEGIN@30
111800µs2.09msMoose::::BEGIN@27Moose::BEGIN@27
111741µs968µsMoose::::BEGIN@31Moose::BEGIN@31
111664µs1.37msMoose::::BEGIN@28Moose::BEGIN@28
111344µs1.39msMoose::::BEGIN@37Moose::BEGIN@37
111337µs858µsMoose::::BEGIN@32Moose::BEGIN@32
111310µs350µsMoose::::BEGIN@12Moose::BEGIN@12
111188µs299µsMoose::::BEGIN@22Moose::BEGIN@22
85299µs10.2msMoose::::hasMoose::has
11171µs1.52msMoose::::init_metaMoose::init_meta
11133µs33µsMoose::::BEGIN@5Moose::BEGIN@5
11116µs19µsMoose::::BEGIN@2Moose::BEGIN@2
11215µs15µsMoose::::bootstrapMoose::bootstrap (xsub)
11113µs30µsMoose::::BEGIN@16Moose::BEGIN@16
11110µs1.31msMoose::::BEGIN@34Moose::BEGIN@34
1119µs26µsMoose::::BEGIN@3Moose::BEGIN@3
1115µs5µsMoose::::BEGIN@21Moose::BEGIN@21
1114µs4µsMoose::::BEGIN@35Moose::BEGIN@35
0000s0sMoose::::__ANON__[:221]Moose::__ANON__[:221]
0000s0sMoose::::_get_callerMoose::_get_caller
0000s0sMoose::::afterMoose::after
0000s0sMoose::::aroundMoose::around
0000s0sMoose::::augmentMoose::augment
0000s0sMoose::::beforeMoose::before
0000s0sMoose::::extendsMoose::extends
0000s0sMoose::::innerMoose::inner
0000s0sMoose::::overrideMoose::override
0000s0sMoose::::superMoose::super
0000s0sMoose::::throw_errorMoose::throw_error
0000s0sMoose::::withMoose::with
Call graph for these subroutines as a Graphviz dot language file.
Line State
ments
Time
on line
Calls Time
in subs
Code
1package Moose;
2325µs223µ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
use strict;
# spent 19µs making 1 call to Moose::BEGIN@2 # spent 3µs making 1 call to strict::import
3325µs244µ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
use warnings;
# spent 26µs making 1 call to Moose::BEGIN@3 # spent 17µs making 1 call to warnings::import
4
5376µs133µs
# spent 33µs within Moose::BEGIN@5 which was called # once (33µs+0s) by SimpleDB::Client::BEGIN@46 at line 5
use 5.008;
# spent 33µs making 1 call to Moose::BEGIN@5
6
71800nsour $VERSION = '0.98';
8116µs$VERSION = eval $VERSION;
91400nsour $AUTHORITY = 'cpan:STEVAN';
10
113112µs22.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
use Scalar::Util 'blessed';
# spent 2.73ms making 1 call to Moose::BEGIN@11 # spent 63µs making 1 call to Exporter::import
123307µs2389µ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
use Carp 'confess';
# spent 350µs making 1 call to Moose::BEGIN@12 # spent 39µs making 1 call to Exporter::import
13
143106µs2172ms
# spent 172ms (3.49+169) within Moose::BEGIN@14 which was called # once (3.49ms+169ms) by SimpleDB::Client::BEGIN@46 at line 14
use Moose::Exporter;
# spent 172ms making 1 call to Moose::BEGIN@14 # spent 22µs making 1 call to Moose::Exporter::import
15
16348µs248µ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
use Class::MOP 0.94;
# spent 30µs making 1 call to Moose::BEGIN@16 # spent 17µs making 1 call to UNIVERSAL::VERSION
17
183123µs121.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
use Moose::Meta::Class;
# spent 21.5ms making 1 call to Moose::BEGIN@18
193110µs117.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
use Moose::Meta::TypeConstraint;
# spent 17.2ms making 1 call to Moose::BEGIN@19
203801µs159.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
use Moose::Meta::TypeCoercion;
# spent 59.7ms making 1 call to Moose::BEGIN@20
21319µs15µs
# spent 5µs within Moose::BEGIN@21 which was called # once (5µs+0s) by SimpleDB::Client::BEGIN@46 at line 21
use Moose::Meta::Attribute;
# spent 5µs making 1 call to Moose::BEGIN@21
223110µs1299µ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
use Moose::Meta::Instance;
# spent 299µs making 1 call to Moose::BEGIN@22
23
243716µs12.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
use Moose::Object;
# spent 2.88ms making 1 call to Moose::BEGIN@24
25
263148µs113.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
use Moose::Meta::Role;
# spent 13.1ms making 1 call to Moose::BEGIN@26
273155µs12.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
use Moose::Meta::Role::Composite;
# spent 2.09ms making 1 call to Moose::BEGIN@27
283108µs11.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
use Moose::Meta::Role::Application;
# spent 1.37ms making 1 call to Moose::BEGIN@28
293109µs11.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
use Moose::Meta::Role::Application::RoleSummation;
# spent 1.92ms making 1 call to Moose::BEGIN@29
303102µs11.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
use Moose::Meta::Role::Application::ToClass;
# spent 1.99ms making 1 call to Moose::BEGIN@30
313102µs1968µ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
use Moose::Meta::Role::Application::ToRole;
# spent 968µs making 1 call to Moose::BEGIN@31
323100µs1858µ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
use Moose::Meta::Role::Application::ToInstance;
# spent 858µs making 1 call to Moose::BEGIN@32
33
34327µs22.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
use Moose::Util::TypeConstraints;
# spent 1.31ms making 1 call to Moose::BEGIN@34 # spent 1.30ms making 1 call to Moose::Exporter::__ANON__[Moose/Exporter.pm:389]
35319µs14µs
# spent 4µs within Moose::BEGIN@35 which was called # once (4µs+0s) by SimpleDB::Client::BEGIN@46 at line 35
use Moose::Util ();
# spent 4µs making 1 call to Moose::BEGIN@35
36
3731.11ms11.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
use Moose::Meta::Attribute::Native;
# spent 1.39ms making 1 call to Moose::BEGIN@37
38
39sub throw_error {
40 # FIXME This
41 shift;
42 goto \&confess
43}
44
45sub 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
56sub 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
sub has {
612861µs my $meta = shift;
62 my $name = shift;
63
64 Moose->throw_error('Usage: has \'name\' => ( key => value, ... )')
65 if @_ % 2 == 1;
66
67 my %options = ( definition_context => Moose::Util::_caller_info(), @_ );
# spent 34µs making 4 calls to Moose::Util::_caller_info, avg 9µs/call
68 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
69 $meta->add_attribute( $_, %options ) for @$attrs;
# spent 4.97ms making 4 calls to Moose::Meta::Class::add_attribute, avg 1.24ms/call
70}
71
72sub before {
73 Moose::Util::add_method_modifier(shift, 'before', \@_);
74}
75
76sub after {
77 Moose::Util::add_method_modifier(shift, 'after', \@_);
78}
79
80sub around {
81 Moose::Util::add_method_modifier(shift, 'around', \@_);
82}
83
841100nsour $SUPER_PACKAGE;
851100nsour $SUPER_BODY;
861200nsour @SUPER_ARGS;
87
88sub 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
95sub override {
96 my $meta = shift;
97 my ( $name, $method ) = @_;
98 $meta->add_override_method_modifier( $name => $method );
99}
100
101sub 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
115sub augment {
116 my $meta = shift;
117 my ( $name, $method ) = @_;
118 $meta->add_augment_method_modifier( $name => $method );
119}
120
12117µs1755µsMoose::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
sub init_meta {
133 # This used to be called as a function. This hack preserves
134 # backwards compatibility.
1351452µs if ( $_[0] ne __PACKAGE__ ) {
136 return __PACKAGE__->init_meta(
137 for_class => $_[0],
138 base_class => $_[1],
139 metaclass => $_[2],
140 );
141 }
142
143 shift;
144 my %args = @_;
145
146 my $class = $args{for_class}
147 or Moose->throw_error("Cannot call init_meta without specifying a for_class");
148 my $base_class = $args{base_class} || 'Moose::Object';
149 my $metaclass = $args{metaclass} || 'Moose::Meta::Class';
150
151 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 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 my $meta;
159
160315µs11µ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 my ( undef, @isa ) = @{ $class->mro::get_linear_isa };
# spent 2µs making 1 call to mro::get_linear_isa
174
175 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 $meta = $metaclass->initialize($class);
# spent 787µs making 1 call to Moose::Meta::Class::initialize
195 }
196
197 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 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
22016µs15µ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 $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 return $meta;
230}
231
232# This may be used in some older MooseX extensions.
233sub _get_caller {
234 goto &Moose::Exporter::_get_caller;
235}
236
237## make 'em all immutable
238
239$_->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
24445118µs4437.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
27410s);
275
276143µs24.89msMoose::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
281136µs1;
282
283__END__
284
285=pod
286
287=head1 NAME
288
289Moose - 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
319Moose is an extension of the Perl 5 object system.
320
321The main goal of Moose is to make Perl 5 Object Oriented programming
322easier, more consistent and less tedious. With Moose you can to think
323more about what you want to do and less about the mechanics of OOP.
324
325Additionally, Moose is built on top of L<Class::MOP>, which is a
326metaclass system for Perl 5. This means that Moose not only makes
327building normal Perl 5 objects better, but it provides the power of
328metaclass programming as well.
329
330=head2 New to Moose?
331
332If you're new to Moose, the best place to start is the
333L<Moose::Manual> docs, followed by the L<Moose::Cookbook>. The intro
334will show you what Moose is, and how it makes Perl 5 OO better.
335
336The cookbook recipes on Moose basics will get you up to speed with
337many of Moose's features quickly. Once you have an idea of what Moose
338can do, you can use the API documentation to get more detail on
339features which interest you.
340
341=head2 Moose Extensions
342
343The C<MooseX::> namespace is the official place to find Moose extensions.
344These extensions can be found on the CPAN. The easiest way to find them
345is to search for them (L<http://search.cpan.org/search?query=MooseX::>),
346or to examine L<Task::Moose> which aims to keep an up-to-date, easily
347installable list of Moose extensions.
348
349=head1 TRANSLATIONS
350
351Much of the Moose documentation has been translated into other languages.
352
353=over 4
354
355=item Japanese
356
357Japanese 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
363Moose makes every attempt to provide as much convenience as possible during
364class construction/definition, but still stay out of your way if you want it
365to. Here are a few items to note when building classes with Moose.
366
367Unless specified with C<extends>, any class which uses Moose will
368inherit from L<Moose::Object>.
369
370Moose will also manage all attributes (including inherited ones) that are
371defined with C<has>. And (assuming you call C<new>, which is inherited from
372L<Moose::Object>) this includes properly initializing all instance slots,
373setting defaults where appropriate, and performing any type constraint checking
374or coercion.
375
376=head1 PROVIDED METHODS
377
378Moose provides a number of methods to all your classes, mostly through the
379inheritance of L<Moose::Object>. There is however, one exception.
380
381=over 4
382
383=item B<meta>
384
385This is a method which provides access to the current class's metaclass.
386
387=back
388
389=head1 EXPORTED FUNCTIONS
390
391Moose will export a number of functions into the class's namespace which
392may then be used to set up the class. These functions all work directly
393on the current class.
394
395=over 4
396
397=item B<extends (@superclasses)>
398
399This function will set the superclass(es) for the current class.
400
401This approach is recommended instead of C<use base>, because C<use base>
402actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
403replace it. This is important to ensure that classes which do not have
404superclasses still properly inherit from L<Moose::Object>.
405
406=item B<with (@roles)>
407
408This will apply a given set of C<@roles> to the local class.
409
410=item B<has $name|@$names =E<gt> %options>
411
412This will install an attribute of a given C<$name> into the current class. If
413the first parameter is an array reference, it will create an attribute for
414every C<$name> in the list. The C<%options> are the same as those provided by
415L<Class::MOP::Attribute>, in addition to the list below which are provided by
416Moose (L<Moose::Meta::Attribute> to be more specific):
417
418=over 4
419
420=item I<is =E<gt> 'rw'|'ro'>
421
422The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
423only). These will create either a read/write accessor or a read-only
424accessor respectively, using the same name as the C<$name> of the attribute.
425
426If you need more control over how your accessors are named, you can
427use the L<reader|Class::MOP::Attribute/reader>,
428L<writer|Class::MOP::Attribute/writer> and
429L<accessor|Class::MOP::Attribute/accessor> options inherited from
430L<Class::MOP::Attribute>, however if you use those, you won't need the
431I<is> option.
432
433=item I<isa =E<gt> $type_name>
434
435The I<isa> option uses Moose's type constraint facilities to set up runtime
436type checking for this attribute. Moose will perform the checks during class
437construction, and within any accessors. The C<$type_name> argument must be a
438string. The string may be either a class name or a type defined using
439Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
440for 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
444This will attempt to use coercion with the supplied type constraint to change
445the value passed into any accessors or constructors. You B<must> have supplied
446a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
447for an example.
448
449=item I<does =E<gt> $role_name>
450
451This will accept the name of a role which the value stored in this attribute
452is expected to have consumed.
453
454=item I<required =E<gt> (1|0)>
455
456This marks the attribute as being required. This means a value must be
457supplied during class construction, I<or> the attribute must be lazy
458and have either a default or a builder. Note that c<required> does not
459say anything about the attribute's value, which can be C<undef>.
460
461=item I<weak_ref =E<gt> (1|0)>
462
463This will tell the class to store the value of this attribute as a weakened
464reference. If an attribute is a weakened reference, it B<cannot> also be
465coerced.
466
467=item I<lazy =E<gt> (1|0)>
468
469This will tell the class to not create this slot until absolutely necessary.
470If an attribute is marked as lazy it B<must> have a default supplied.
471
472=item I<auto_deref =E<gt> (1|0)>
473
474This tells the accessor to automatically dereference the value of this
475attribute when called in list context. The accessor will still return a
476reference when called in scalar context. If this behavior isn't desirable,
477L<Moose::Meta::Attribute::Native::Trait::Array/elements> or
478L<Moose::Meta::Attribute::Native::Trait::Hash/elements> may be a better
479choice. The I<auto_deref> option is only legal if your I<isa> option is
480either C<ArrayRef> or C<HashRef>.
481
482=item I<trigger =E<gt> $code>
483
484The I<trigger> option is a CODE reference which will be called after
485the value of the attribute is set. The CODE ref will be passed the
486instance itself and the updated value. If the attribute already had a
487value, this will be passed as the third value to the trigger.
488
489You B<can> have a trigger on a read-only attribute.
490
491B<NOTE:> Triggers will only fire when you B<assign> to the attribute,
492either in the constructor, or using the writer. Default and built values will
493B<not> cause the trigger to be fired.
494
495=item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | DUCKTYPE | CODE>
496
497The I<handles> option provides Moose classes with automated delegation features.
498This is a pretty complex and powerful option. It accepts many different option
499formats, each with its own benefits and drawbacks.
500
501B<NOTE:> The class being delegated to does not need to be a Moose based class,
502which is why this feature is especially useful when wrapping non-Moose classes.
503
504All I<handles> option formats share the following traits:
505
506You cannot override a locally defined method with a delegated method; an
507exception will be thrown if you try. That is to say, if you define C<foo> in
508your class, you cannot override it with a delegated C<foo>. This is almost never
509something you would want to do, and if it is, you should do it by hand and not
510use Moose.
511
512You cannot override any of the methods found in Moose::Object, or the C<BUILD>
513and C<DEMOLISH> methods. These will not throw an exception, but will silently
514move on to the next method in the list. My reasoning for this is that you would
515almost never want to do this, since it usually breaks your class. As with
516overriding locally defined methods, if you do want to do this, you should do it
517manually, not with Moose.
518
519You do not I<need> to have a reader (or accessor) for the attribute in order
520to delegate to it. Moose will create a means of accessing the value for you,
521however this will be several times B<less> efficient then if you had given
522the attribute a reader (or accessor) to use.
523
524Below is the documentation for each option format:
525
526=over 4
527
528=item C<ARRAY>
529
530This is the most common usage for I<handles>. You basically pass a list of
531method names to be delegated, and Moose will install a delegation method
532for each one.
533
534=item C<HASH>
535
536This is the second most common usage for I<handles>. Instead of a list of
537method names, you pass a HASH ref where each key is the method name you
538want installed locally, and its value is the name of the original method
539in the class being delegated to.
540
541This can be very useful for recursive classes like trees. Here is a
542quick 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
565In this example, the Tree package gets C<parent_node> and C<siblings> methods,
566which delegate to the C<node> and C<children> methods (respectively) of the Tree
567instance stored in the C<parent> slot.
568
569You 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
578The first element of the array reference is the original method name, and the
579rest is a list of curried arguments.
580
581=item C<REGEXP>
582
583The regexp option works very similar to the ARRAY option, except that it builds
584the list of methods for you. It starts by collecting all possible methods of the
585class being delegated to, then filters that list using the regexp supplied here.
586
587B<NOTE:> An I<isa> option is required when using the regexp option format. This
588is so that we can determine (at compile time) the method list from the class.
589Without an I<isa> this is just not possible.
590
591=item C<ROLE>
592
593With the role option, you specify the name of a role whose "interface" then
594becomes the list of methods to handle. The "interface" can be defined as; the
595methods of the role and any required methods of the role. It should be noted
596that this does B<not> include any method modifiers or generated attribute
597methods (which is consistent with role composition).
598
599=item C<DUCKTYPE>
600
601With the duck type option, you pass a duck type object whose "interface" then
602becomes the list of methods to handle. The "interface" can be defined as; the
603list of methods passed to C<duck_type> to create a duck type object. For more
604information on C<duck_type> please check
605L<Moose::Util::TypeConstraints>.
606
607=item C<CODE>
608
609This is the option to use when you really want to do something funky. You should
610only use it if you really know what you are doing, as it involves manual
611metaclass twiddling.
612
613This takes a code reference, which should expect two arguments. The first is the
614attribute meta-object this I<handles> is attached to. The second is the
615metaclass of the class being delegated to. It expects you to return a hash (not
616a HASH ref) of the methods you want mapped.
617
618=back
619
620=item I<metaclass =E<gt> $metaclass_name>
621
622This tells the class to use a custom attribute metaclass for this particular
623attribute. Custom attribute metaclasses are useful for extending the
624capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
625but they are still a fairly advanced topic and too much to cover here, see
626L<Moose::Cookbook::Meta::Recipe1> for more information.
627
628See L<Metaclass and Trait Name Resolution> for details on how a metaclass name
629is resolved to a class name.
630
631=item I<traits =E<gt> [ @role_names ]>
632
633This tells Moose to take the list of C<@role_names> and apply them to the
634attribute meta-object. This is very similar to the I<metaclass> option, but
635allows you to use more than one extension at a time.
636
637See L<Metaclass and Trait Name Resolution> for details on how a trait name is
638resolved to a role name.
639
640Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait
641example.
642
643=item I<builder> => Str
644
645The value of this key is the name of the method that will be called to
646obtain the value used to initialize the attribute. See the L<builder
647option 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
652The value of this key is the default value which will initialize the attribute.
653
654NOTE: If the value is a simple scalar (string or number), then it can
655be just passed as is. However, if you wish to initialize it with a
656HASH or ARRAY ref, then you need to wrap that inside a CODE reference.
657See the L<default option docs in
658Class::MOP::Attribute|Class::MOP::Attribute/default> for more
659information.
660
661=item I<clearer> => Str
662
663Creates a method allowing you to clear the value, see the L<clearer option
664docs in Class::MOP::Attribute|Class::MOP::Attribute/clearer> for more
665information.
666
667=item I<predicate> => Str
668
669Creates a method to perform a basic test to see if a value has been set in the
670attribute, see the L<predicate option docs in
671Class::MOP::Attribute|Class::MOP::Attribute/predicate> for more information.
672
673=item I<lazy_build> => (0|1)
674
675Automatically 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
680This may be a method name (referring to a method on the class with
681this attribute) or a CODE ref. The initializer is used to set the
682attribute value on an instance when the attribute is set during
683instance initialization (but not when the value is being assigned
684to). See the L<initializer option docs in
685Class::MOP::Attribute|Class::MOP::Attribute/initializer> for more
686information.
687
688=item I<documentation> => $string
689
690An 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
699This is variation on the normal attribute creator C<has> which allows you to
700clone and extend an attribute from a superclass or from a role. Here is an
701example 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
719What is happening here is that B<My::Foo> is cloning the C<message> attribute
720from 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
723Here 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
741In this case, we are basically taking the attribute which the role supplied
742and altering it within the bounds of this feature.
743
744Note that you can only extend an attribute from either a superclass or a role,
745you cannot extend an attribute in a role that composes over an attribute from
746another role.
747
748Aside from where the attributes come from (one from superclass, the other
749from a role), this feature works exactly the same. This feature is restricted
750somewhat, so as to try and force at least I<some> sanity into it. You are only
751allowed to change the following attributes:
752
753=over 4
754
755=item I<default>
756
757Change the default value of an attribute.
758
759=item I<coerce>
760
761Change whether the attribute attempts to coerce a value passed to it.
762
763=item I<required>
764
765Change if the attribute is required to have a value.
766
767=item I<documentation>
768
769Change the documentation string associated with the attribute.
770
771=item I<lazy>
772
773Change if the attribute lazily initializes the slot.
774
775=item I<isa>
776
777You I<are> allowed to change the type without restriction.
778
779It is recommended that you use this freedom with caution. We used to
780only allow for extension only if the type was a subtype of the parent's
781type, but we felt that was too restrictive and is better left as a
782policy decision.
783
784=item I<handles>
785
786You are allowed to B<add> a new C<handles> definition, but you are B<not>
787allowed to I<change> one.
788
789=item I<builder>
790
791You are allowed to B<add> a new C<builder> definition, but you are B<not>
792allowed to I<change> one.
793
794=item I<metaclass>
795
796You are allowed to B<add> a new C<metaclass> definition, but you are
797B<not> allowed to I<change> one.
798
799=item I<traits>
800
801You are allowed to B<add> additional traits to the C<traits> definition.
802These traits will be composed into the attribute, but preexisting traits
803B<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
813These three items are syntactic sugar for the before, after, and around method
814modifier features that L<Class::MOP> provides. More information on these may be
815found in L<Moose::Manual::MethodModifiers> and the
816L<Class::MOP::Class documentation|Class::MOP::Class/"Method Modifiers">.
817
818=item B<super>
819
820The keyword C<super> is a no-op when called outside of an C<override> method. In
821the context of an C<override> method, it will call the next most appropriate
822superclass method with the same arguments as the original method.
823
824=item B<override ($name, &sub)>
825
826An C<override> method is a way of explicitly saying "I am overriding this
827method from my superclass". You can call C<super> within this method, and
828it will work as expected. The same thing I<can> be accomplished with a normal
829method call and the C<SUPER::> pseudo-package; it is really your choice.
830
831=item B<inner>
832
833The keyword C<inner>, much like C<super>, is a no-op outside of the context of
834an C<augment> method. You can think of C<inner> as being the inverse of
835C<super>; the details of how C<inner> and C<augment> work is best described in
836the L<Moose::Cookbook::Basics::Recipe6>.
837
838=item B<augment ($name, &sub)>
839
840An C<augment> method, is a way of explicitly saying "I am augmenting this
841method from my superclass". Once again, the details of how C<inner> and
842C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>.
843
844=item B<confess>
845
846This is the C<Carp::confess> function, and exported here because I use it
847all the time.
848
849=item B<blessed>
850
851This is the C<Scalar::Util::blessed> function, it is exported here because I
852use it all the time. It is highly recommended that this is used instead of
853C<ref> anywhere you need to test for an object's class name.
854
855=back
856
857=head1 METACLASS
858
859When you use Moose, you can specify which metaclass to use:
860
861 use Moose -metaclass => 'My::Meta::Class';
862
863You can also specify traits which will be applied to your metaclass:
864
865 use Moose -traits => 'My::Trait';
866
867This is very similar to the attribute traits feature. When you do
868this, your class's C<meta> object will have the specified traits
869applied to it. See L<Metaclass and Trait Name Resolution> for more
870details.
871
872=head2 Metaclass and Trait Name Resolution
873
874By default, when given a trait name, Moose simply tries to load a
875class of the same name. If such a class does not exist, it then looks
876for for a class matching
877B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type>
878variable here will be one of B<Attribute> or B<Class>, depending on
879what the trait is being applied to.
880
881If a class with this long name exists, Moose checks to see if it has
882the method C<register_implementation>. This method is expected to
883return the I<real> class name of the trait. If there is no
884C<register_implementation> method, it will fall back to using
885B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name.
886
887The lookup method for metaclasses is the same, except that it looks
888for a class matching B<Moose::Meta::$type::Custom::$metaclass_name>.
889
890If all this is confusing, take a look at
891L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an
892attribute trait.
893
894=head1 UNIMPORTING FUNCTIONS
895
896=head2 B<unimport>
897
898Moose offers a way to remove the keywords it exports, through the C<unimport>
899method. You simply have to say C<no Moose> at the bottom of your code for this
900to 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
917To learn more about extending Moose, we recommend checking out the
918"Extending" recipes in the L<Moose::Cookbook>, starting with
919L<Moose::Cookbook::Extending::Recipe1>, which provides an overview of
920all the different ways you might extend Moose.
921
922=head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >>
923
924The C<init_meta> method sets up the metaclass object for the class
925specified by C<for_class>. This method injects a a C<meta> accessor
926into the class so you can get at this object. It also sets the class's
927superclass to C<base_class>, with L<Moose::Object> as the default.
928
929C<init_meta> returns the metaclass object for C<$class>.
930
931You can specify an alternate metaclass with the C<metaclass> option.
932
933For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>.
934
935This method used to be documented as a function which accepted
936positional parameters. This calling style will still work for
937backwards compatibility, but is deprecated.
938
939=head2 B<import>
940
941Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
942and C<{into_level =E<gt> 1}>.
943
944B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter>
945instead, which lets you stack multiple C<Moose.pm>-alike modules
946sanely. It handles getting the exported functions into the right place
947for you.
948
949=head2 B<throw_error>
950
951An alias for C<confess>, used by internally by Moose.
952
953=head1 METACLASS COMPATIBILITY AND MOOSE
954
955Metaclass compatibility is a thorny subject. You should start by
956reading the "About Metaclass compatibility" section in the
957C<Class::MOP> docs.
958
959Moose will attempt to resolve a few cases of metaclass incompatibility
960when you set the superclasses for a class, unlike C<Class::MOP>, which
961simply dies if the metaclasses are incompatible.
962
963In actuality, Moose fixes incompatibility for I<all> of a class's
964metaclasses, not just the class metaclass. That includes the instance
965metaclass, attribute metaclass, as well as its constructor class and
966destructor class. However, for simplicity this discussion will just
967refer to "metaclass", meaning the class metaclass, most of the time.
968
969Moose has two algorithms for fixing metaclass incompatibility.
970
971The first algorithm is very simple. If all the metaclass for the
972parent is a I<subclass> of the child's metaclass, then we simply
973replace the child's metaclass with the parent's.
974
975The second algorithm is more complicated. It tries to determine if the
976metaclasses only "differ by roles". This means that the parent and
977child's metaclass share a common ancestor in their respective
978hierarchies, and that the subclasses under the common ancestor are
979only different because of role applications. This case is actually
980fairly common when you mix and match various C<MooseX::*> modules,
981many of which apply roles to the metaclass.
982
983If the parent and child do differ by roles, Moose replaces the
984metaclass in the child with a newly created metaclass. This metaclass
985is a subclass of the parent's metaclass, does all of the roles that
986the child's metaclass did before being replaced. Effectively, this
987means the new metaclass does all of the roles done by both the
988parent's and child's original metaclasses.
989
990Ultimately, this is all transparent to you except in the case of an
991unresolvable conflict.
992
993=head2 The MooseX:: namespace
994
995Generally if you're writing an extension I<for> Moose itself you'll want
996to put your extension in the C<MooseX::> namespace. This namespace is
997specifically for extensions that make Moose better or different in some
998fundamental way. It is traditionally B<not> for a package that just happens
999to use Moose. This namespace follows from the examples of the C<LWPx::>
1000and C<DBIx::> namespaces that perform the same function for C<LWP> and C<DBI>
1001respectively.
1002
1003=head1 CAVEATS
1004
1005=over 4
1006
1007=item *
1008
1009It should be noted that C<super> and C<inner> B<cannot> be used in the same
1010method. However, they may be combined within the same class hierarchy; see
1011F<t/014_override_augment_inner_super.t> for an example.
1012
1013The reason for this is that C<super> is only valid within a method
1014with the C<override> modifier, and C<inner> will never be valid within an
1015C<override> method. In fact, C<augment> will skip over any C<override> methods
1016when searching for its appropriate C<inner>.
1017
1018This might seem like a restriction, but I am of the opinion that keeping these
1019two features separate (yet interoperable) actually makes them easy to use, since
1020their behavior is then easier to predict. Time will tell whether I am right or
1021not (UPDATE: so far so good).
1022
1023=back
1024
1025=head1 GETTING HELP
1026
1027We offer both a mailing list and a very active IRC channel.
1028
1029The mailing list is L<moose@perl.org>. You must be subscribed to send
1030a message. To subscribe, send an empty message to
1031L<moose-subscribe@perl.org>
1032
1033You can also visit us at C<#moose> on L<irc://irc.perl.org/#moose>
1034This channel is quite active, and questions at all levels (on Moose-related
1035topics ;) 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,
1046and it certainly wouldn't have this name ;P
1047
1048=item The basis of the TypeContraints module was Rob Kinyon's idea
1049originally, I just ran with it.
1050
1051=item Thanks to mst & chansen and the whole #moose posse for all the
1052early 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
1064This is the official web home of Moose, it contains links to our public SVN repository
1065as well as links to a number of talks and articles on Moose and Moose related
1066technologies.
1067
1068=item The Moose is flying, a tutorial by Randal Schwartz
1069
1070Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html>
1071
1072Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html>
1073
1074=item Several Moose extension modules in the C<MooseX::> namespace.
1075
1076See 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
1088I mention this in the L<Class::MOP> docs too, this book was critical in
1089the 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
1099This paper (suggested by lbr on #moose) was what lead to the implementation
1100of the C<super>/C<override> and C<inner>/C<augment> features. If you really
1101want to understand them, I suggest you read this.
1102
1103=back
1104
1105=head1 BUGS
1106
1107All complex software has bugs lurking in it, and this module is no
1108exception.
1109
1110Please report any bugs to C<bug-moose@rt.cpan.org>, or through the web
1111interface at L<http://rt.cpan.org>.
1112
1113You can also discuss feature requests or possible bugs on the Moose mailing
1114list (moose@perl.org) or on IRC at L<irc://irc.perl.org/#moose>.
1115
1116=head1 FEATURE REQUESTS
1117
1118We are very strict about what features we add to the Moose core, especially
1119the user-visible features. Instead we have made sure that the underlying
1120meta-system of Moose is as extensible as possible so that you can add your
1121own features easily.
1122
1123That said, occasionally there is a feature needed in the meta-system
1124to support your planned extension, in which case you should either
1125email the mailing list (moose@perl.org) or join us on IRC at
1126L<irc://irc.perl.org/#moose> to discuss. The
1127L<Moose::Manual::Contributing> has more detail about how and when you
1128can contribute.
1129
1130=head1 AUTHOR
1131
1132Moose is an open project, there are at this point dozens of people who have
1133contributed, and can contribute. If you have added anything to the Moose
1134project you have a commit bit on this file and can add your name to the list.
1135
1136=head2 CABAL
1137
1138However there are only a few people with the rights to release a new version
1139of Moose. The Moose Cabal are the people to go to with questions regarding
1140the wider purview of Moose, and help out maintaining not just the code
1141but the community as well.
1142
1143Stevan (stevan) Little E<lt>stevan@iinteractive.comE<gt>
1144
1145Jesse (doy) Luehrs E<lt>doy at tozt dot netE<gt>
1146
1147Yuval (nothingmuch) Kogman
1148
1149Shawn (sartak) Moore E<lt>sartak@bestpractical.comE<gt>
1150
1151Hans Dieter (confound) Pearcey E<lt>hdp@pobox.comE<gt>
1152
1153Chris (perigrin) Prather
1154
1155Florian Ragwitz E<lt>rafl@debian.orgE<gt>
1156
1157Dave (autarch) Rolsky E<lt>autarch@urth.orgE<gt>
1158
1159=head2 OTHER CONTRIBUTORS
1160
1161Aankhen
1162
1163Adam (Alias) Kennedy
1164
1165Anders (Debolaz) Nor Berle
1166
1167Nathan (kolibrie) Gray
1168
1169Christian (chansen) Hansen
1170
1171Eric (ewilhelm) Wilhelm
1172
1173Guillermo (groditi) Roditi
1174
1175Jess (castaway) Robinson
1176
1177Matt (mst) Trout
1178
1179Robert (phaylon) Sedlacek
1180
1181Robert (rlb3) Boone
1182
1183Scott (konobi) McWhirter
1184
1185Shlomi (rindolf) Fish
1186
1187Wallace (wreis) Reis
1188
1189Jonathan (jrockway) Rockway
1190
1191Piotr (dexter) Roszatycki
1192
1193Sam (mugwump) Vilain
1194
1195Cory (gphat) Watson
1196
1197Dylan Hardison (doc fixes)
1198
1199... and many other #moose folks
1200
1201=head1 COPYRIGHT AND LICENSE
1202
1203Copyright 2006-2010 by Infinity Interactive, Inc.
1204
1205L<http://www.iinteractive.com>
1206
1207This library is free software; you can redistribute it and/or modify
1208it 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
sub Moose::bootstrap; # xsub