8 our $AUTHORITY = 'cpan:STEVAN';
10 use Scalar::Util 'blessed', 'reftype';
11 use Carp 'confess', 'croak';
12 use Sub::Name 'subname';
18 use Moose::Meta::Class;
19 use Moose::Meta::TypeConstraint;
20 use Moose::Meta::TypeConstraint::Class;
21 use Moose::Meta::TypeCoercion;
22 use Moose::Meta::Attribute;
23 use Moose::Meta::Instance;
25 use Moose::Meta::Role;
28 use Moose::Util::TypeConstraints;
35 my ( $class, $base_class, $metaclass ) = @_;
36 $base_class = 'Moose::Object' unless defined $base_class;
37 $metaclass = 'Moose::Meta::Class' unless defined $metaclass;
40 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
41 unless $metaclass->isa('Moose::Meta::Class');
43 # make a subtype for each Moose class
45 unless find_type_constraint($class);
48 if ( $class->can('meta') ) {
50 # this is the case where the metaclass pragma
51 # was used before the 'use Moose' statement to
52 # override a specific class
53 $meta = $class->meta();
54 ( blessed($meta) && $meta->isa('Moose::Meta::Class') )
55 || confess "You already have a &meta function, but it does not return a Moose::Meta::Class";
59 # this is broken currently, we actually need
60 # to allow the possiblity of an inherited
61 # meta, which will not be visible until the
62 # user 'extends' first. This needs to have
63 # more intelligence to it
64 $meta = $metaclass->initialize($class);
67 # re-initialize so it inherits properly
68 $metaclass->initialize( blessed( $_[0] ) || $_[0] );
73 # make sure they inherit from Moose::Object
74 $meta->superclasses($base_class)
75 unless $meta->superclasses();
83 return subname 'Moose::extends' => sub (@) {
84 confess "Must derive at least one class" unless @_;
87 foreach my $super (@supers) {
88 Class::MOP::load_class($super);
91 # this checks the metaclass to make sure
92 # it is correct, sometimes it can get out
93 # of sync when the classes are being built
94 my $meta = $class->meta->_fix_metaclass_incompatability(@supers);
95 $meta->superclasses(@supers);
100 return subname 'Moose::with' => sub (@) {
101 Moose::Util::apply_all_roles($class->meta, @_)
106 return subname 'Moose::has' => sub ($;%) {
108 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
110 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
111 $class->meta->add_attribute( $_, %options ) for @$attrs;
116 return subname 'Moose::before' => sub (@&) {
118 my $meta = $class->meta;
119 $meta->add_before_method_modifier( $_, $code ) for @_;
124 return subname 'Moose::after' => sub (@&) {
126 my $meta = $class->meta;
127 $meta->add_after_method_modifier( $_, $code ) for @_;
132 return subname 'Moose::around' => sub (@&) {
134 my $meta = $class->meta;
135 $meta->add_around_method_modifier( $_, $code ) for @_;
142 $SUPER_SLOT{$CALLER} = \*{"${CALLER}::super"};
144 return subname 'Moose::super' => sub { };
148 return subname 'Moose::override' => sub ($&) {
149 my ( $name, $method ) = @_;
150 $class->meta->add_override_method_modifier( $name => $method );
157 $INNER_SLOT{$CALLER} = \*{"${CALLER}::inner"};
159 return subname 'Moose::inner' => sub { };
163 return subname 'Moose::augment' => sub (@&) {
164 my ( $name, $method ) = @_;
165 $class->meta->add_augment_method_modifier( $name => $method );
168 make_immutable => sub {
170 return subname 'Moose::make_immutable' => sub {
171 warn "The make_immutable keyword has been deprecated, " .
172 "please go back to __PACKAGE__->meta->make_immutable\n";
173 $class->meta->make_immutable(@_);
177 return \&Carp::confess;
180 return \&Scalar::Util::blessed;
184 my $exporter = Sub::Exporter::build_exporter(
186 exports => \%exports,
187 groups => { default => [':all'] }
191 # 1 extra level because it's called by import so there's a layer of indirection
195 ref $_[1] && defined $_[1]->{into}
197 : ref $_[1] && defined $_[1]->{into_level}
198 ? caller($offset + $_[1]->{into_level})
203 $CALLER = _get_caller(@_);
205 # this works because both pragmas set $^H (see perldoc perlvar)
206 # which affects the current compilation - i.e. the file who use'd
207 # us - which is why we don't need to do anything special to make
208 # it affect that file rather than this one (which is already compiled)
213 # we should never export to main
214 return if $CALLER eq 'main';
216 init_meta( $CALLER, 'Moose::Object' );
223 my $class = _get_caller(@_);
225 # loop through the exports ...
226 foreach my $name ( keys %exports ) {
229 if ( defined &{ $class . '::' . $name } ) {
230 my $keyword = \&{ $class . '::' . $name };
232 # make sure it is from Moose
233 my ($pkg_name) = Class::MOP::get_code_info($keyword);
235 next if $pkg_name ne 'Moose';
237 # and if it is from Moose then undef the slot
238 delete ${ $class . '::' }{$name};
245 ## make 'em all immutable
247 $_->meta->make_immutable(
248 inline_constructor => 0,
249 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
252 'Moose::Meta::Attribute',
253 'Moose::Meta::Class',
254 'Moose::Meta::Instance',
256 'Moose::Meta::TypeConstraint',
257 'Moose::Meta::TypeConstraint::Union',
258 'Moose::Meta::TypeConstraint::Parameterized',
259 'Moose::Meta::TypeCoercion',
261 'Moose::Meta::Method',
262 'Moose::Meta::Method::Accessor',
263 'Moose::Meta::Method::Constructor',
264 'Moose::Meta::Method::Destructor',
265 'Moose::Meta::Method::Overriden',
268 'Moose::Meta::Role::Method',
269 'Moose::Meta::Role::Method::Required',
280 Moose - A postmodern object system for Perl 5
285 use Moose; # automatically turns on strict and warnings
287 has 'x' => (is => 'rw', isa => 'Int');
288 has 'y' => (is => 'rw', isa => 'Int');
301 has 'z' => (is => 'rw', isa => 'Int');
303 after 'clear' => sub {
310 Moose is an extension of the Perl 5 object system.
312 =head2 Another object system!?!?
314 Yes, I know there has been an explosion recently of new ways to
315 build object's in Perl 5, most of them based on inside-out objects
316 and other such things. Moose is different because it is not a new
317 object system for Perl 5, but instead an extension of the existing
320 Moose is built on top of L<Class::MOP>, which is a metaclass system
321 for Perl 5. This means that Moose not only makes building normal
322 Perl 5 objects better, but it also provides the power of metaclass
325 =head2 Is this for real? Or is this just an experiment?
327 Moose is I<based> on the prototypes and experiments I did for the Perl 6
328 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
330 =head2 Is this ready for use in production?
332 Yes, I believe that it is.
334 Moose has been used successfully in production environemnts by several people
335 and companies (including the one I work for). There are Moose applications
336 which have been in production with little or no issue now for well over a year.
337 I consider it highly stable and we are commited to keeping it stable.
339 Of course, in the end, you need to make this call yourself. If you have
340 any questions or concerns, please feel free to email me, or even the list
341 or just stop by #moose and ask away.
343 =head2 Is Moose just Perl 6 in Perl 5?
345 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
346 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
347 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
348 instead of switching to Ruby, I wrote Moose :)
350 =head2 Wait, I<post> modern, I thought it was just I<modern>?
352 So I was reading Larry Wall's talk from the 1999 Linux World entitled
353 "Perl, the first postmodern computer language" in which he talks about how
354 he picked the features for Perl because he thought they were cool and he
355 threw out the ones that he thought sucked. This got me thinking about how
356 we have done the same thing in Moose. For Moose, we have "borrowed" features
357 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
358 the bits we didn't like (cause they sucked) we tossed aside. So for this
359 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
363 =head2 Moose Extensions
365 The L<MooseX::> namespace is the official place to find Moose extensions.
366 There are a number of these modules out on CPAN right now the best way to
367 find them is to search for MooseX:: on search.cpan.org.
369 =head1 BUILDING CLASSES WITH MOOSE
371 Moose makes every attempt to provide as much convenience as possible during
372 class construction/definition, but still stay out of your way if you want it
373 to. Here are a few items to note when building classes with Moose.
375 Unless specified with C<extends>, any class which uses Moose will
376 inherit from L<Moose::Object>.
378 Moose will also manage all attributes (including inherited ones) that are
379 defined with C<has>. And (assuming you call C<new>, which is inherited from
380 L<Moose::Object>) this includes properly initializing all instance slots,
381 setting defaults where appropriate, and performing any type constraint checking
384 =head1 PROVIDED METHODS
386 Moose provides a number of methods to all your classes, mostly through the
387 inheritance of L<Moose::Object>. There is however, one exception.
393 This is a method which provides access to the current class's metaclass.
397 =head1 EXPORTED FUNCTIONS
399 Moose will export a number of functions into the class's namespace which
400 may then be used to set up the class. These functions all work directly
401 on the current class.
405 =item B<extends (@superclasses)>
407 This function will set the superclass(es) for the current class.
409 This approach is recommended instead of C<use base>, because C<use base>
410 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
411 replace it. This is important to ensure that classes which do not have
412 superclasses still properly inherit from L<Moose::Object>.
414 =item B<with (@roles)>
416 This will apply a given set of C<@roles> to the local class.
418 =item B<has $name =E<gt> %options>
420 This will install an attribute of a given C<$name> into the current class.
421 The C<%options> are the same as those provided by
422 L<Class::MOP::Attribute>, in addition to the list below which are provided
423 by Moose (L<Moose::Meta::Attribute> to be more specific):
427 =item I<is =E<gt> 'rw'|'ro'>
429 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
430 only). These will create either a read/write accessor or a read-only
431 accessor respectively, using the same name as the C<$name> of the attribute.
433 If you need more control over how your accessors are named, you can use the
434 I<reader>, I<writer> and I<accessor> options inherited from
435 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
438 =item I<isa =E<gt> $type_name>
440 The I<isa> option uses Moose's type constraint facilities to set up runtime
441 type checking for this attribute. Moose will perform the checks during class
442 construction, and within any accessors. The C<$type_name> argument must be a
443 string. The string may be either a class name or a type defined using
444 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
445 for information on how to define a new type, and how to retrieve type meta-data).
447 =item I<coerce =E<gt> (1|0)>
449 This will attempt to use coercion with the supplied type constraint to change
450 the value passed into any accessors or constructors. You B<must> have supplied
451 a type constraint in order for this to work. See L<Moose::Cookbook::Recipe5>
454 =item I<does =E<gt> $role_name>
456 This will accept the name of a role which the value stored in this attribute
457 is expected to have consumed.
459 =item I<required =E<gt> (1|0)>
461 This marks the attribute as being required. This means a I<defined> value must be
462 supplied during class construction, and the attribute may never be set to
463 C<undef> with an accessor.
465 =item I<weak_ref =E<gt> (1|0)>
467 This will tell the class to store the value of this attribute as a weakened
468 reference. If an attribute is a weakened reference, it B<cannot> also be
471 =item I<lazy =E<gt> (1|0)>
473 This will tell the class to not create this slot until absolutely necessary.
474 If an attribute is marked as lazy it B<must> have a default supplied.
476 =item I<auto_deref =E<gt> (1|0)>
478 This tells the accessor whether to automatically dereference the value returned.
479 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
481 =item I<trigger =E<gt> $code>
483 The I<trigger> option is a CODE reference which will be called after the value of
484 the attribute is set. The CODE ref will be passed the instance itself, the
485 updated value and the attribute meta-object (this is for more advanced fiddling
486 and can typically be ignored). You B<cannot> have a trigger on a read-only
489 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
491 The I<handles> option provides Moose classes with automated delegation features.
492 This is a pretty complex and powerful option. It accepts many different option
493 formats, each with its own benefits and drawbacks.
495 B<NOTE:> The class being delegated to does not need to be a Moose based class,
496 which is why this feature is especially useful when wrapping non-Moose classes.
498 All I<handles> option formats share the following traits:
500 You cannot override a locally defined method with a delegated method; an
501 exception will be thrown if you try. That is to say, if you define C<foo> in
502 your class, you cannot override it with a delegated C<foo>. This is almost never
503 something you would want to do, and if it is, you should do it by hand and not
506 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
507 and C<DEMOLISH> methods. These will not throw an exception, but will silently
508 move on to the next method in the list. My reasoning for this is that you would
509 almost never want to do this, since it usually breaks your class. As with
510 overriding locally defined methods, if you do want to do this, you should do it
511 manually, not with Moose.
513 You do not I<need> to have a reader (or accessor) for the attribute in order
514 to delegate to it. Moose will create a means of accessing the value for you,
515 however this will be several times B<less> efficient then if you had given
516 the attribute a reader (or accessor) to use.
518 Below is the documentation for each option format:
524 This is the most common usage for I<handles>. You basically pass a list of
525 method names to be delegated, and Moose will install a delegation method
530 This is the second most common usage for I<handles>. Instead of a list of
531 method names, you pass a HASH ref where each key is the method name you
532 want installed locally, and its value is the name of the original method
533 in the class being delegated to.
535 This can be very useful for recursive classes like trees. Here is a
536 quick example (soon to be expanded into a Moose::Cookbook::Recipe):
541 has 'node' => (is => 'rw', isa => 'Any');
546 default => sub { [] }
554 parent_node => 'node',
555 siblings => 'children',
559 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
560 which delegate to the C<node> and C<children> methods (respectively) of the Tree
561 instance stored in the C<parent> slot.
565 The regexp option works very similar to the ARRAY option, except that it builds
566 the list of methods for you. It starts by collecting all possible methods of the
567 class being delegated to, then filters that list using the regexp supplied here.
569 B<NOTE:> An I<isa> option is required when using the regexp option format. This
570 is so that we can determine (at compile time) the method list from the class.
571 Without an I<isa> this is just not possible.
575 With the role option, you specify the name of a role whose "interface" then
576 becomes the list of methods to handle. The "interface" can be defined as; the
577 methods of the role and any required methods of the role. It should be noted
578 that this does B<not> include any method modifiers or generated attribute
579 methods (which is consistent with role composition).
583 This is the option to use when you really want to do something funky. You should
584 only use it if you really know what you are doing, as it involves manual
587 This takes a code reference, which should expect two arguments. The first is the
588 attribute meta-object this I<handles> is attached to. The second is the
589 metaclass of the class being delegated to. It expects you to return a hash (not
590 a HASH ref) of the methods you want mapped.
594 =item I<metaclass =E<gt> $metaclass_name>
596 This tells the class to use a custom attribute metaclass for this particular
597 attribute. Custom attribute metaclasses are useful for extending the
598 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
599 but they are still a fairly advanced topic and too much to cover here, see
600 L<Moose::Cookbook::Recipe11> for more information.
602 The default behavior here is to just load C<$metaclass_name>; however, we also
603 have a way to alias to a shorter name. This will first look to see if
604 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
605 will then check to see if that has the method C<register_implementation>, which
606 should return the actual name of the custom attribute metaclass. If there is no
607 C<register_implementation> method, it will fall back to using
608 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
610 =item I<traits =E<gt> [ @role_names ]>
612 This tells Moose to take the list of C<@role_names> and apply them to the
613 attribute meta-object. This is very similar to the I<metaclass> option, but
614 allows you to use more than one extension at a time. This too is an advanced
615 topic, we don't yet have a cookbook for it though.
617 As with I<metaclass>, the default behavior is to just load C<$role_name>; however,
618 we also have a way to alias to a shorter name. This will first look to see if
619 B<Moose::Meta::Attribute::Custom::Trait::$role_name> exists. If it does, Moose
620 will then check to see if that has the method C<register_implementation>, which
621 should return the actual name of the custom attribute trait. If there is no
622 C<register_implementation> method, it will fall back to using
623 B<Moose::Meta::Attribute::Custom::Trait::$metaclass_name> as the trait name.
627 =item B<has +$name =E<gt> %options>
629 This is variation on the normal attibute creator C<has> which allows you to
630 clone and extend an attribute from a superclass or from a role. Here is an
631 example of the superclass usage:
639 default => 'Hello, I am a Foo'
647 has '+message' => (default => 'Hello I am My::Foo');
649 What is happening here is that B<My::Foo> is cloning the C<message> attribute
650 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
651 'Str'> characteristics, but changing the value in C<default>.
653 Here is another example, but within the context of a role:
661 default => 'Hello, I am a Foo'
669 has '+message' => (default => 'Hello I am My::Foo');
671 In this case, we are basically taking the attribute which the role supplied
672 and altering it within the bounds of this feature.
674 Aside from where the attributes come from (one from superclass, the other
675 from a role), this feature works exactly the same. This feature is restricted
676 somewhat, so as to try and force at least I<some> sanity into it. You are only
677 allowed to change the following attributes:
683 Change the default value of an attribute.
687 Change whether the attribute attempts to coerce a value passed to it.
691 Change if the attribute is required to have a value.
693 =item I<documentation>
695 Change the documentation string associated with the attribute.
699 Change if the attribute lazily initializes the slot.
703 You I<are> allowed to change the type without restriction.
705 It is recommended that you use this freedom with caution. We used to
706 only allow for extension only if the type was a subtype of the parent's
707 type, but we felt that was too restrictive and is better left as a
712 You are allowed to B<add> a new C<handles> definition, but you are B<not>
713 allowed to I<change> one.
717 You are allowed to B<add> a new C<builder> definition, but you are B<not>
718 allowed to I<change> one.
722 =item B<before $name|@names =E<gt> sub { ... }>
724 =item B<after $name|@names =E<gt> sub { ... }>
726 =item B<around $name|@names =E<gt> sub { ... }>
728 This three items are syntactic sugar for the before, after, and around method
729 modifier features that L<Class::MOP> provides. More information on these may be
730 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
735 The keyword C<super> is a no-op when called outside of an C<override> method. In
736 the context of an C<override> method, it will call the next most appropriate
737 superclass method with the same arguments as the original method.
739 =item B<override ($name, &sub)>
741 An C<override> method is a way of explicitly saying "I am overriding this
742 method from my superclass". You can call C<super> within this method, and
743 it will work as expected. The same thing I<can> be accomplished with a normal
744 method call and the C<SUPER::> pseudo-package; it is really your choice.
748 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
749 an C<augment> method. You can think of C<inner> as being the inverse of
750 C<super>; the details of how C<inner> and C<augment> work is best described in
751 the L<Moose::Cookbook::Recipe7>.
753 =item B<augment ($name, &sub)>
755 An C<augment> method, is a way of explicitly saying "I am augmenting this
756 method from my superclass". Once again, the details of how C<inner> and
757 C<augment> work is best described in the L<Moose::Cookbook::Recipe7>.
761 This is the C<Carp::confess> function, and exported here because I use it
766 This is the C<Scalar::Util::blessed> function, it is exported here because I
767 use it all the time. It is highly recommended that this is used instead of
768 C<ref> anywhere you need to test for an object's class name.
772 =head1 UNIMPORTING FUNCTIONS
776 Moose offers a way to remove the keywords it exports, through the C<unimport>
777 method. You simply have to say C<no Moose> at the bottom of your code for this
778 to work. Here is an example:
783 has 'first_name' => (is => 'rw', isa => 'Str');
784 has 'last_name' => (is => 'rw', isa => 'Str');
788 $self->first_name . ' ' . $self->last_name
791 no Moose; # keywords are removed from the Person package
793 =head1 EXTENDING AND EMBEDDING MOOSE
795 Moose also offers some options for extending or embedding it into your own
796 framework. The basic premise is to have something that sets up your class'
797 metaclass and export the moose declarators (C<has>, C<with>, C<extends>,...).
804 my $CALLER = caller();
809 # we should never export to main
810 return if $CALLER eq 'main';
811 Moose::init_meta( $CALLER, 'MyFramework::Base' );
812 Moose->import({into => $CALLER});
814 # Do my custom framework stuff
821 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
822 and C<{into_level =E<gt> 1}>
824 =head2 B<init_meta ($class, $baseclass, $metaclass)>
826 Moose does some boot strapping: it creates a metaclass object for your class,
827 and then injects a C<meta> accessor into your class to retrieve it. Then it
828 sets your baseclass to Moose::Object or the value you pass in unless you already
829 have one. This is all done via C<init_meta> which takes the name of your class
830 and optionally a baseclass and a metaclass as arguments.
838 It should be noted that C<super> and C<inner> B<cannot> be used in the same
839 method. However, they may be combined within the same class hierarchy; see
840 F<t/014_override_augment_inner_super.t> for an example.
842 The reason for this is that C<super> is only valid within a method
843 with the C<override> modifier, and C<inner> will never be valid within an
844 C<override> method. In fact, C<augment> will skip over any C<override> methods
845 when searching for its appropriate C<inner>.
847 This might seem like a restriction, but I am of the opinion that keeping these
848 two features separate (yet interoperable) actually makes them easy to use, since
849 their behavior is then easier to predict. Time will tell whether I am right or
850 not (UPDATE: so far so good).
854 It is important to note that we currently have no simple way of combining
855 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
856 and that in many cases they will conflict with one another. We are working on
857 developing a way around this issue, but in the meantime, you have been warned.
861 =head1 ACKNOWLEDGEMENTS
865 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
867 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
869 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
870 and it certainly wouldn't have this name ;P
872 =item The basis of the TypeContraints module was Rob Kinyon's idea
873 originally, I just ran with it.
875 =item Thanks to mst & chansen and the whole #moose posse for all the
876 early ideas/feature-requests/encouragement/bug-finding.
878 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
886 =item L<http://www.iinteractive.com/moose>
888 This is the official web home of Moose, it contains links to our public SVN repo
889 as well as links to a number of talks and articles on Moose and Moose related
892 =item L<Class::MOP> documentation
894 =item The #moose channel on irc.perl.org
896 =item The Moose mailing list - moose@perl.org
898 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/5788>
900 =item Several Moose extension modules in the L<MooseX::> namespace.
908 =item The Art of the MetaObject Protocol
910 I mention this in the L<Class::MOP> docs too, this book was critical in
911 the development of both modules and is highly recommended.
919 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
921 This paper (suggested by lbr on #moose) was what lead to the implementation
922 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
923 want to understand them, I suggest you read this.
929 All complex software has bugs lurking in it, and this module is no
930 exception. If you find a bug please either email me, or add the bug
935 Stevan Little E<lt>stevan@iinteractive.comE<gt>
937 B<with contributions from:>
943 Anders (Debolaz) Nor Berle
945 Nathan (kolibre) Gray
947 Christian (chansen) Hansen
949 Hans Dieter (confound) Pearcey
951 Eric (ewilhelm) Wilhelm
953 Guillermo (groditi) Roditi
955 Jess (castaway) Robinson
959 Robert (phaylon) Sedlacek
963 Scott (konobi) McWhirter
965 Shlomi (rindolf) Fish
967 Yuval (nothingmuch) Kogman
969 Chris (perigrin) Prather
971 Jonathan (jrockway) Rockway
973 Piotr (dexter) Roszatycki
979 ... and many other #moose folks
981 =head1 COPYRIGHT AND LICENSE
983 Copyright 2006-2008 by Infinity Interactive, Inc.
985 L<http://www.iinteractive.com>
987 This library is free software; you can redistribute it and/or modify
988 it under the same terms as Perl itself.