5 Moose::Manual::Attributes - Object attributes with Moose
9 Moose attributes have many properties, and attributes are probably the
10 single most powerful and flexible part of Moose. You can create a
11 powerful class simply by declaring attributes. In fact, it's possible
12 to have classes that consist solely of attribute declarations.
14 An attribute is a property that every member of a class has. For
15 example, we might say that "every C<Person> object has a first name and
16 last name". Attributes can be optional, so that we can say "some C<Person>
17 objects have a social security number (and some don't)".
19 At its simplest, an attribute can be thought of as a named value (as
20 in a hash) that can be read and set. However, attributes can also have
21 defaults, type constraints, delegation and much more.
23 In other languages, attributes are also referred to as slots or
26 =head1 ATTRIBUTE OPTIONS
28 Use the C<has> function to declare an attribute:
34 has 'first_name' => ( is => 'rw' );
36 This says that all C<Person> objects have an optional read-write
37 "first_name" attribute.
39 =head2 Read-write Vs read-only
41 The options passed to C<has> define the properties of the
42 attribute. There are a many options, but in the simplest form you just
43 need to set C<is>, which can be either C<rw> (read-write) or C<ro>
46 (In fact, you could even omit C<is>, but that gives you an attribute
47 that has no accessors, which is pointless unless you're doing some
50 =head2 Accessor methods
52 Each attribute has one or more accessor methods. An accessor lets you
53 read and write the value of that attribute for an object.
55 By default, the accessor method has the same name as the attribute. If
56 you declared your attribute as C<ro> then your accessor will be
57 read-only. If you declared it read-write, you get a read-write
60 Given our C<Person> example above, we now have a single C<first_name>
61 accessor that can read or write a C<Person> object's C<first_name>
64 If you want, you can also explicitly specify the method names to be
65 used for reading and writing an attribute's value. This is
66 particularly handy when you'd like an attribute to be publicly
67 readable, but only privately settable. For example:
71 writer => '_set_weight',
74 This might be useful if weight is calculated based on other methods,
75 for example every time the C<eat> method is called, we might adjust
76 weight. This lets us hide the implementation details of weight
77 changes, but still provide the weight value to users of the class.
79 Some people might prefer to have distinct methods for reading and
80 writing. In I<Perl Best Practices>, Damian Conway recommends that
81 reader methods start with "get_" and writer methods start with "set_".
83 We can do exactly that by providing names for both the C<reader> and
88 reader => 'get_weight',
89 writer => 'set_weight',
92 If you're thinking that doing this over and over would be insanely
93 tedious, you're right! Fortunately, Moose provides a powerful
94 extension system that lets override the default naming
95 conventions. See L<Moose::Manual::MooseX> for more details.
97 =head2 Predicate and clearer methods
99 Moose allows you to explicitly distinguish between a false or
100 undefined attribute value and an attribute which has not been set. If
101 you want to access this information, you must define clearer and
102 predicate methods for an attribute.
104 A predicate method tells you whether or not a given attribute is
105 currently set. Note an attribute can be explicitly set to C<undef> or
106 some other false value, but the predicate will return true.
108 The clearer method unsets the attribute. This is I<not> the
109 same as setting the value to C<undef>, but you can only distinguish
110 between them if you define a predicate method!
112 Here's some code to illustrate the relationship between an accessor,
113 predicate, and clearer method.
121 clearer => 'clear_ssn',
122 predicate => 'has_ssn',
127 my $person = Person->new();
128 $person->has_ssn; # false
131 $person->ssn; # returns undef
132 $person->has_ssn; # true
135 $person->ssn; # returns undef
136 $person->has_ssn; # false
138 $person->ssn('123-45-6789');
139 $person->ssn; # returns '123-45-6789'
140 $person->has_ssn; # true
142 my $person2 = Person->new( ssn => '111-22-3333');
143 $person2->has_ssn; # true
145 By default, Moose does not make a predicate or clearer for you. You
146 must explicitly provide names for them.
148 =head2 Required or not?
150 By default, all attributes are optional, and do not need to be
151 provided at object construction time. If you want to make an attribute
152 required, simply set the C<required> option to true:
159 There are a couple caveats worth mentioning in regards to what
160 "required" actually means.
162 Basically, all it says is that this attribute (C<name>) must be provided
163 to the constructor. It does not say anything about its value, so it
166 If you define a clearer method on a required attribute, the clearer
167 I<will> work, so even a required attribute can be unset after object
170 This means that if you do make an attribute required, providing a
171 clearer doesn't make much sense. In some cases, it might be handy to
172 have a I<private> C<clearer> and C<predicate> for a required
175 =head2 Default and builder methods
177 Attributes can have default values, and Moose provides two ways to
178 specify that default.
180 In the simplest form, you simply provide a non-reference scalar value
181 for the C<default> option:
186 predicate => 'has_size',
189 If the size attribute is not provided to the constructor, then it ends
190 up being set to C<medium>:
192 my $person = Person->new();
193 $person->size; # medium
194 $person->has_size; # true
196 You can also provide a subroutine reference for C<default>. This
197 reference will be called as a method on the object.
202 sub { ( 'small', 'medium', 'large' )[ int( rand 3 ) ] },
203 predicate => 'has_size',
206 This is dumb example, but it illustrates the point that the subroutine
207 will be called for every new object created.
209 When you provide a C<default> subroutine reference, it is called as a
210 method on the object, with no additional parameters:
217 return $self->height > 200 ? 'big' : 'average';
221 When the C<default> is called during object construction, it may be
222 called before other attributes have been set. If your default is
223 dependent on other parts of the object's state, you can make the
224 attribute C<lazy>. Laziness is covered in the next section.
226 If you want to use a reference of any sort as the default value, you
227 must return it from a subroutine. This is necessary because otherwise
228 Perl would instantiate the reference exactly once, and it would be
229 shared by all objects:
233 default => {}, # wrong!
236 Moose will throw an error if you pass a bare non-subroutine reference
239 If Moose allowed this then the default mapping attribute could easily
240 end up shared across many objects. Instead, wrap it in a subroutine
245 default => sub { {} }, # right!
248 This is a bit awkward, but it's just the way Perl works.
250 As an alternative to using a subroutine reference, you can instead
251 supply a C<builder> method for your attribute:
255 builder => '_build_size',
256 predicate => 'has_size',
260 return ( 'small', 'medium', 'large' )[ int( rand 3 ) ];
263 This has several advantages. First, it moves a chunk of code to its
264 own named method, which improves readability and code
267 We strongly recommend that you use a C<builder> instead of a
268 C<default> for anything beyond the most trivial default.
270 A C<builder>, just like a C<default>, is called as a method on the
271 object with no additional parameters.
273 =head3 Builders allow subclassing
275 Because the C<builder> is called I<by name>, it goes through Perl's
276 method resolution. This means that builder methods are both
277 inheritable and overridable.
279 If we subclass our C<Person> class, we can override C<_build_size>:
286 sub _build_size { return 'small' }
288 =head3 Builders can be composed from roles
290 Because builders are called by name, they work well with roles. For
291 example, a role could provide an attribute but require that the
292 consuming class provide the C<builder>:
297 requires '_build_size';
302 builder => '_build_size',
310 sub _build_size { return 'small' }
312 Roles are covered in L<Moose::Manual::Roles>.
314 =head2 Laziness and C<lazy_build>
316 Moose lets you defer attribute population by making an attribute
322 builder => '_build_size',
325 When C<lazy> is true, the default is not generated until the reader
326 method is called, rather than at object construction time. There are
327 several reasons you might choose to do this.
329 First, if the default value for this attribute depends on some other
330 attributes, then the attribute I<must> be C<lazy>. During object
331 construction, defaults are not generated in a predictable order, so
332 you cannot count on some other attribute being populated when
333 generating a default.
335 Second, there's often no reason to calculate a default before it's
336 needed. Making an attribute C<lazy> lets you defer the cost until the
337 attribute is needed. If the attribute is I<never> needed, you save
340 We recommend that you make any attribute with a builder or non-trivial
341 default C<lazy> as a matter of course.
343 To facilitate this, you can simply specify the C<lazy_build> attribute
344 option. This bundles up a number of options together:
351 This is the same as specifying all of these options:
356 builder => '_build_size',
357 clearer => 'clear_size',
358 predicate => 'has_size',
361 If your attribute name starts with an underscore (C<_>), then the clearer
362 and predicate will as well:
374 builder => '_build__size',
375 clearer => '_clear_size',
376 predicate => '_has_size',
379 Note the doubled underscore in the builder name. Internally, Moose
380 simply prepends the attribute name with "_build_" to come up with the
383 If you don't like the names that C<lazy_build> generates, you can
384 always provide your own:
389 clearer => '_clear_size',
392 Options that you explicitly provide are always used in favor of
393 Moose's internal defaults.
395 =head2 Constructor parameters (C<init_arg>)
397 By default, each attribute can be passed by name to the class's
398 constructor. On occasion, you may want to use a different name for
399 the constructor parameter. You may also want to make an attribute
400 unsettable via the constructor.
402 Both of these goals can be accomplished with the C<init_arg> option:
409 Now we have an attribute named "bigness", but we pass C<size> to the
412 Even more useful is the ability to disable setting an attribute via
413 the constructor. This is particularly handy for private attributes:
415 has '_genetic_code' => (
421 By setting the C<init_arg> to C<undef>, we make it impossible to set
422 this attribute when creating a new object.
424 =head2 Weak references
426 Moose has built-in support for weak references. If you set the
427 C<weak_ref> option to a true value, then it will call
428 C<Scalar::Util::weaken> whenever the attribute is set:
435 $node->parent($parent_node);
437 This is very useful when you're building objects that may contain
442 A C<trigger> is a subroutine that is called whenever the attribute is
447 trigger => \&_size_set,
451 my ( $self, $size ) = @_;
453 warn $self->name, " size is now $size\n";
456 The trigger is called as a method, and receives the new value as its argument.
457 The trigger is called I<after> the value is set.
459 This differs from an after method modifier in two ways. First, a
460 trigger is only called when the attribute is set, as opposed to
461 whenever the accessor method is called (for reading or
462 writing). Second, it is also called if the when an attribute's value
463 is passed to the constructor.
465 However, triggers are I<not> called when an attribute is populated
466 from a C<default> or C<builder>
468 =head2 Attribute types
470 Attributes can be restricted to only accept certain types:
472 has 'first_name' => (
477 This says that the C<first_name> attribute must be a string.
479 Moose also provides a shortcut for specifying that an attribute only
480 accepts objects that do a certain role:
484 does => 'MyApp::Weapon',
487 See the L<Moose::Manual::Types> documentation for a complete
488 discussion of Moose's type system.
492 Attributes can define methods which simply delegate to their values:
494 has 'hair_color' => (
496 isa => 'Graphics::Color::RGB',
497 handles => { hair_color_hex => 'as_hex_string' },
500 This adds a new method, C<hair_color_hex>. When someone calls
501 C<hair_color_hex>, internally, the object just calls C<<
502 $self->hair_color->as_hex_string >>.
504 See L<Moose::Manual::Delegation> for documentation on how to set up
507 =head2 Metaclass and traits
509 One of Moose's best features is that it can be extended in all sorts
510 of ways through the use of custom metaclasses and metaclass traits.
512 When declaring an attribute, you can declare a metaclass or a set of
513 traits for the attribute:
515 use MooseX::AttributeHelpers;
518 metaclass => 'Collection::Hash',
520 default => sub { {} },
523 In this case, the metaclass C<Collection::Hash> really refers to
524 L<MooseX::AttributeHelpers::Collection::Hash>.
526 You can also apply one or more traits to an attribute:
528 use MooseX::MetaDescription;
532 traits => ['MooseX::MetaDescription::Meta::Trait'],
534 html_widget => 'text_input',
535 serialize_as => 'element',
539 The advantage of traits is that you can mix more than one of them
540 together easily (in fact, a trait is just a role under the hood).
542 There are a number of MooseX modules on CPAN which provide useful
543 attribute metaclasses and traits. See L<Moose::Manual::MooseX> for
544 some examples. You can also write your own metaclasses and traits. See
545 the "Meta" and "Extending" recipes in L<Moose::Cookbook> for examples.
547 =head1 ATTRIBUTE INHERITANCE
549 By default, a child inherits all of its parent class(es)' attributes
550 as-is. However, you can explicitly change some aspects of the
551 inherited attribute in the child class.
553 The options that can be overridden in a subclass are:
563 =item * documentation
579 To override an attribute, you simply prepend its name with a plus sign
588 has '+first_name' => (
593 Now the C<first_name> attribute in C<LazyPerson> is lazy, and defaults
596 We recommend that you exercise caution when changing the type (C<isa>)
597 of an inherited attribute.
599 =head1 MORE ON ATTRIBUTES
601 Moose attributes are a big topic, and this document glosses over a few
602 aspects of their aspects. We recommend that you read the
603 L<Moose::Manual::Delegation> and L<Moose::Manual::Types> documents to
604 get a more complete understanding of attribute features.
606 =head1 A FEW MORE OPTIONS
608 Moose has lots of attribute options. The ones listed below are
609 superseded by some more modern features, but are covered for the sake
612 =head2 The C<documentation> option
614 You can provide a piece of documentation as a string for an attribute:
616 has 'first_name' => (
618 documentation => q{The person's first (personal) name},
621 Moose does absolutely nothing with this information other than store
624 =head2 The C<auto_deref> option
626 If your attribute is an array reference or hash reference, the
627 C<auto_deref> option will make Moose dereference the value when it is
628 returned from the reader method:
630 my %map = $object->mapping;
632 This option only works if your attribute is explicitly typed as an
633 C<ArrayRef> or C<HashRef>.
635 However, we recommend that you use L<MooseX::AttributeHelpers> for
636 these types of attributes, which gives you much more control over how
637 they are accessed and manipulated.
641 Moose provides an attribute option called C<initializer>. This is
642 similar to C<builder>, except that it is I<only> called during object
645 This option is inherited from L<Class::MOP>, but we recommend that you
646 use a C<builder> (which is Moose-only) instead.
650 Dave Rolsky E<lt>autarch@urth.orgE<gt>
652 =head1 COPYRIGHT AND LICENSE
654 Copyright 2009 by Infinity Interactive, Inc.
656 L<http://www.iinteractive.com>
658 This library is free software; you can redistribute it and/or modify
659 it under the same terms as Perl itself.