X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FMoose.pm;h=0b499267770f0bb73634313665d41eb363db318f;hb=6d5cbd2b637d672d74ad86d5309580f142ee3439;hp=40f4650c0dcf6aed51fc5ded3d15cafd3f9d5be9;hpb=29db16a9aa7532a01390dddb9fc5dee43429a12a;p=gitmo%2FMoose.git diff --git a/lib/Moose.pm b/lib/Moose.pm index 40f4650..0b49926 100644 --- a/lib/Moose.pm +++ b/lib/Moose.pm @@ -1,87 +1,272 @@ -use lib '/Users/stevan/CPAN/Class-MOP/Class-MOP/lib'; - package Moose; use strict; use warnings; -our $VERSION = '0.01'; +our $VERSION = '0.39'; +our $AUTHORITY = 'cpan:STEVAN'; -use Scalar::Util 'blessed'; +use Scalar::Util 'blessed', 'reftype'; use Carp 'confess'; use Sub::Name 'subname'; +use Sub::Exporter; + +use Class::MOP 0.51; + use Moose::Meta::Class; +use Moose::Meta::TypeConstraint; +use Moose::Meta::TypeConstraint::Class; +use Moose::Meta::TypeCoercion; use Moose::Meta::Attribute; +use Moose::Meta::Instance; + +use Moose::Meta::Role; use Moose::Object; +use Moose::Util::TypeConstraints; +use Moose::Util (); + +{ + my $CALLER; + + sub init_meta { + my ( $class, $base_class, $metaclass ) = @_; + $base_class = 'Moose::Object' unless defined $base_class; + $metaclass = 'Moose::Meta::Class' unless defined $metaclass; + + confess + "The Metaclass $metaclass must be a subclass of Moose::Meta::Class." + unless $metaclass->isa('Moose::Meta::Class'); + + # make a subtype for each Moose class + class_type($class) + unless find_type_constraint($class); + + my $meta; + if ( $class->can('meta') ) { + # NOTE: + # this is the case where the metaclass pragma + # was used before the 'use Moose' statement to + # override a specific class + $meta = $class->meta(); + ( blessed($meta) && $meta->isa('Moose::Meta::Class') ) + || confess "You already have a &meta function, but it does not return a Moose::Meta::Class"; + } + else { + # NOTE: + # this is broken currently, we actually need + # to allow the possiblity of an inherited + # meta, which will not be visible until the + # user 'extends' first. This needs to have + # more intelligence to it + $meta = $metaclass->initialize($class); + $meta->add_method( + 'meta' => sub { + # re-initialize so it inherits properly + $metaclass->initialize( blessed( $_[0] ) || $_[0] ); + } + ); + } + + # make sure they inherit from Moose::Object + $meta->superclasses($base_class) + unless $meta->superclasses(); + + return $meta; + } + + my %exports = ( + extends => sub { + my $class = $CALLER; + return subname 'Moose::extends' => sub (@) { + confess "Must derive at least one class" unless @_; + + my @supers = @_; + foreach my $super (@supers) { + Class::MOP::load_class($super); + } + + # this checks the metaclass to make sure + # it is correct, sometimes it can get out + # of sync when the classes are being built + my $meta = $class->meta->_fix_metaclass_incompatability(@supers); + $meta->superclasses(@supers); + }; + }, + with => sub { + my $class = $CALLER; + return subname 'Moose::with' => sub (@) { + Moose::Util::apply_all_roles($class->meta, @_) + }; + }, + has => sub { + my $class = $CALLER; + return subname 'Moose::has' => sub ($;%) { + my $name = shift; + die 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1; + my %options = @_; + my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ]; + $class->meta->add_attribute( $_, %options ) for @$attrs; + }; + }, + before => sub { + my $class = $CALLER; + return subname 'Moose::before' => sub (@&) { + my $code = pop @_; + my $meta = $class->meta; + $meta->add_before_method_modifier( $_, $code ) for @_; + }; + }, + after => sub { + my $class = $CALLER; + return subname 'Moose::after' => sub (@&) { + my $code = pop @_; + my $meta = $class->meta; + $meta->add_after_method_modifier( $_, $code ) for @_; + }; + }, + around => sub { + my $class = $CALLER; + return subname 'Moose::around' => sub (@&) { + my $code = pop @_; + my $meta = $class->meta; + $meta->add_around_method_modifier( $_, $code ) for @_; + }; + }, + super => sub { + { + our %SUPER_SLOT; + no strict 'refs'; + $SUPER_SLOT{$CALLER} = \*{"${CALLER}::super"}; + } + return subname 'Moose::super' => sub { }; + }, + override => sub { + my $class = $CALLER; + return subname 'Moose::override' => sub ($&) { + my ( $name, $method ) = @_; + $class->meta->add_override_method_modifier( $name => $method ); + }; + }, + inner => sub { + { + our %INNER_SLOT; + no strict 'refs'; + $INNER_SLOT{$CALLER} = \*{"${CALLER}::inner"}; + } + return subname 'Moose::inner' => sub { }; + }, + augment => sub { + my $class = $CALLER; + return subname 'Moose::augment' => sub (@&) { + my ( $name, $method ) = @_; + $class->meta->add_augment_method_modifier( $name => $method ); + }; + }, + make_immutable => sub { + my $class = $CALLER; + return subname 'Moose::make_immutable' => sub { + $class->meta->make_immutable(@_); + }; + }, + confess => sub { + return \&Carp::confess; + }, + blessed => sub { + return \&Scalar::Util::blessed; + }, + ); + + my $exporter = Sub::Exporter::build_exporter( + { + exports => \%exports, + groups => { default => [':all'] } + } + ); + + # 1 extra level because it's called by import so there's a layer of indirection + sub _get_caller{ + my $offset = 1; + return + ref $_[1] && defined $_[1]->{into} + ? $_[1]->{into} + : ref $_[1] && defined $_[1]->{into_level} + ? caller($offset + $_[1]->{into_level}) + : caller($offset); + } + + sub import { + $CALLER = _get_caller(@_); + + # this works because both pragmas set $^H (see perldoc perlvar) + # which affects the current compilation - i.e. the file who use'd + # us - which is why we don't need to do anything special to make + # it affect that file rather than this one (which is already compiled) + + strict->import; + warnings->import; + + # we should never export to main + return if $CALLER eq 'main'; + + init_meta( $CALLER, 'Moose::Object' ); + + goto $exporter; + } + + sub unimport { + no strict 'refs'; + my $class = _get_caller(@_); + + # loop through the exports ... + foreach my $name ( keys %exports ) { + + # if we find one ... + if ( defined &{ $class . '::' . $name } ) { + my $keyword = \&{ $class . '::' . $name }; + + # make sure it is from Moose + my ($pkg_name) = Class::MOP::get_code_info($keyword); + next if $@; + next if $pkg_name ne 'Moose'; + + # and if it is from Moose then undef the slot + delete ${ $class . '::' }{$name}; + } + } + } -require Moose::Util::TypeConstraints; - -sub import { - shift; - my $pkg = caller(); - - Moose::Util::TypeConstraints->import($pkg); - - my $meta; - if ($pkg->can('meta')) { - $meta = $pkg->meta(); - (blessed($meta) && $meta->isa('Class::MOP::Class')) - || confess "Whoops, not møøsey enough"; - } - else { - $meta = Moose::Meta::Class->initialize($pkg => ( - ':attribute_metaclass' => 'Moose::Meta::Attribute' - )); - } - - # NOTE: - # &alias_method will install the method, but it - # will not name it with - - # handle superclasses - $meta->alias_method('extends' => subname 'Moose::extends' => sub { $meta->superclasses(@_) }); - - # handle attributes - $meta->alias_method('has' => subname 'Moose::has' => sub { - my ($name, %options) = @_; - if (exists $options{is}) { - $options{type_constraint} = $options{is}; - } - elsif (exists $options{isa}) { - $options{type_constraint} = Moose::Util::TypeConstraints::subtype( - Object => Moose::Util::TypeConstraints::where { $_->isa($options{isa}) } - ); - } - $meta->add_attribute($name, %options) - }); - - # handle method modifers - $meta->alias_method('before' => subname 'Moose::before' => sub { - my $code = pop @_; - $meta->add_before_method_modifier($_, $code) for @_; - }); - $meta->alias_method('after' => subname 'Moose::after' => sub { - my $code = pop @_; - $meta->add_after_method_modifier($_, $code) for @_; - }); - $meta->alias_method('around' => subname 'Moose::around' => sub { - my $code = pop @_; - $meta->add_around_method_modifier($_, $code) for @_; - }); - - # make sure they inherit from Moose::Object - $meta->superclasses('Moose::Object') - unless $meta->superclasses(); - - # we recommend using these things - # so export them for them - $meta->alias_method('confess' => \&confess); - $meta->alias_method('blessed' => \&blessed); } +## make 'em all immutable + +$_->meta->make_immutable( + inline_constructor => 0, + inline_accessors => 1, # these are Class::MOP accessors, so they need inlining + ) + for ( + 'Moose::Meta::Attribute', + 'Moose::Meta::Class', + 'Moose::Meta::Instance', + + 'Moose::Meta::TypeConstraint', + 'Moose::Meta::TypeConstraint::Union', + 'Moose::Meta::TypeConstraint::Parameterized', + 'Moose::Meta::TypeCoercion', + + 'Moose::Meta::Method', + 'Moose::Meta::Method::Accessor', + 'Moose::Meta::Method::Constructor', + 'Moose::Meta::Method::Destructor', + 'Moose::Meta::Method::Overriden', + + 'Moose::Meta::Role', + 'Moose::Meta::Role::Method', + 'Moose::Meta::Role::Method::Required', + ); + 1; __END__ @@ -90,46 +275,672 @@ __END__ =head1 NAME -Moose - +Moose - A postmodern object system for Perl 5 =head1 SYNOPSIS - + + package Point; + use Moose; # automatically turns on strict and warnings + + has 'x' => (is => 'rw', isa => 'Int'); + has 'y' => (is => 'rw', isa => 'Int'); + + sub clear { + my $self = shift; + $self->x(0); + $self->y(0); + } + + package Point3D; + use Moose; + + extends 'Point'; + + has 'z' => (is => 'rw', isa => 'Int'); + + after 'clear' => sub { + my $self = shift; + $self->z(0); + }; + =head1 DESCRIPTION -=head1 OTHER NAMES +Moose is an extension of the Perl 5 object system. -Makes Other Object Systems Envious +=head2 Another object system!?!? -Most Other Objects Suck Eggs +Yes, I know there has been an explosion recently of new ways to +build object's in Perl 5, most of them based on inside-out objects +and other such things. Moose is different because it is not a new +object system for Perl 5, but instead an extension of the existing +object system. -Makes Object Orientation So Easy +Moose is built on top of L, which is a metaclass system +for Perl 5. This means that Moose not only makes building normal +Perl 5 objects better, but it also provides the power of metaclass +programming. -Metacircular Object Oriented Systems Environment +=head2 Is this for real? Or is this just an experiment? -=head1 BUGS +Moose is I on the prototypes and experiments I did for the Perl 6 +meta-model. However, Moose is B an experiment/prototype; it is for B. -All complex software has bugs lurking in it, and this module is no -exception. If you find a bug please either email me, or add the bug -to cpan-RT. +=head2 Is this ready for use in production? + +Yes, I believe that it is. + +Moose has been used successfully in production environemnts by several people +and companies (including the one I work for). There are Moose applications +which have been in production with little or no issue now for well over a year. +I consider it highly stable and we are commited to keeping it stable. + +Of course, in the end, you need to make this call yourself. If you have +any questions or concerns, please feel free to email me, or even the list +or just stop by #moose and ask away. + +=head2 Is Moose just Perl 6 in Perl 5? + +No. While Moose is very much inspired by Perl 6, it is not itself Perl 6. +Instead, it is an OO system for Perl 5. I built Moose because I was tired of +writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So +instead of switching to Ruby, I wrote Moose :) + +=head2 Wait, I modern, I thought it was just I? + +So I was reading Larry Wall's talk from the 1999 Linux World entitled +"Perl, the first postmodern computer language" in which he talks about how +he picked the features for Perl because he thought they were cool and he +threw out the ones that he thought sucked. This got me thinking about how +we have done the same thing in Moose. For Moose, we have "borrowed" features +from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and +the bits we didn't like (cause they sucked) we tossed aside. So for this +reason (and a few others) I have re-dubbed Moose a I object system. + +Nuff Said. + +=head2 Moose Extensions + +The L namespace is the official place to find Moose extensions. +There are a number of these modules out on CPAN right now the best way to +find them is to search for MooseX:: on search.cpan.org. + +=head1 BUILDING CLASSES WITH MOOSE + +Moose makes every attempt to provide as much convenience as possible during +class construction/definition, but still stay out of your way if you want it +to. Here are a few items to note when building classes with Moose. + +Unless specified with C, any class which uses Moose will +inherit from L. + +Moose will also manage all attributes (including inherited ones) that are +defined with C. And (assuming you call C, which is inherited from +L) this includes properly initializing all instance slots, +setting defaults where appropriate, and performing any type constraint checking +or coercion. + +=head1 EXPORTED FUNCTIONS + +Moose will export a number of functions into the class's namespace which +may then be used to set up the class. These functions all work directly +on the current class. + +=over 4 + +=item B + +This is a method which provides access to the current class's metaclass. + +=item B + +This function will set the superclass(es) for the current class. + +This approach is recommended instead of C, because C +actually Ces onto the class's C<@ISA>, whereas C will +replace it. This is important to ensure that classes which do not have +superclasses still properly inherit from L. + +=item B + +This will apply a given set of C<@roles> to the local class. Role support +is currently under heavy development; see L for more details. + +=item B %options> + +This will install an attribute of a given C<$name> into the current class. +The C<%options> are the same as those provided by +L, in addition to the list below which are provided +by Moose (L to be more specific): + +=over 4 + +=item I 'rw'|'ro'> + +The I option accepts either I (for read/write) or I (for read +only). These will create either a read/write accessor or a read-only +accessor respectively, using the same name as the C<$name> of the attribute. + +If you need more control over how your accessors are named, you can use the +I, I and I options inherited from +L. + +=item I $type_name> + +The I option uses Moose's type constraint facilities to set up runtime +type checking for this attribute. Moose will perform the checks during class +construction, and within any accessors. The C<$type_name> argument must be a +string. The string may be either a class name or a type defined using +Moose's type definition features. (Refer to L +for information on how to define a new type, and how to retrieve type meta-data). + +=item I (1|0)> + +This will attempt to use coercion with the supplied type constraint to change +the value passed into any accessors or constructors. You B have supplied +a type constraint in order for this to work. See L +for an example. + +=item I $role_name> + +This will accept the name of a role which the value stored in this attribute +is expected to have consumed. + +=item I (1|0)> + +This marks the attribute as being required. This means a I value must be +supplied during class construction, and the attribute may never be set to +C with an accessor. + +=item I (1|0)> + +This will tell the class to store the value of this attribute as a weakened +reference. If an attribute is a weakened reference, it B also be +coerced. + +=item I (1|0)> + +This will tell the class to not create this slot until absolutely necessary. +If an attribute is marked as lazy it B have a default supplied. + +=item I (1|0)> + +This tells the accessor whether to automatically dereference the value returned. +This is only legal if your C option is either C or C. + +=item I $metaclass_name> + +This tells the class to use a custom attribute metaclass for this particular +attribute. Custom attribute metaclasses are useful for extending the +capabilities of the I keyword: they are the simplest way to extend the MOP, +but they are still a fairly advanced topic and too much to cover here. I will +try and write a recipe on them soon. + +The default behavior here is to just load C<$metaclass_name>; however, we also +have a way to alias to a shorter name. This will first look to see if +B exists. If it does, Moose +will then check to see if that has the method C, which +should return the actual name of the custom attribute metaclass. If there is no +C method, it will fall back to using +B as the metaclass name. + +=item I $code> + +The I option is a CODE reference which will be called after the value of +the attribute is set. The CODE ref will be passed the instance itself, the +updated value and the attribute meta-object (this is for more advanced fiddling +and can typically be ignored). You B have a trigger on a read-only +attribute. + +=item I ARRAY | HASH | REGEXP | ROLE | CODE> + +The I option provides Moose classes with automated delegation features. +This is a pretty complex and powerful option. It accepts many different option +formats, each with its own benefits and drawbacks. + +B This feature is no longer experimental, but it may still have subtle +bugs lurking in the deeper corners. If you think you have found a bug, you +probably have, so please report it to me right away. + +B The class being delegated to does not need to be a Moose based class, +which is why this feature is especially useful when wrapping non-Moose classes. + +All I option formats share the following traits: + +You cannot override a locally defined method with a delegated method; an +exception will be thrown if you try. That is to say, if you define C in +your class, you cannot override it with a delegated C. This is almost never +something you would want to do, and if it is, you should do it by hand and not +use Moose. + +You cannot override any of the methods found in Moose::Object, or the C +and C methods. These will not throw an exception, but will silently +move on to the next method in the list. My reasoning for this is that you would +almost never want to do this, since it usually breaks your class. As with +overriding locally defined methods, if you do want to do this, you should do it +manually, not with Moose. + +You do not I to have a reader (or accessor) for the attribute in order +to delegate to it. Moose will create a means of accessing the value for you, +however this will be several times B efficient then if you had given +the attribute a reader (or accessor) to use. + +Below is the documentation for each option format: + +=over 4 + +=item C + +This is the most common usage for I. You basically pass a list of +method names to be delegated, and Moose will install a delegation method +for each one. + +=item C + +This is the second most common usage for I. Instead of a list of +method names, you pass a HASH ref where each key is the method name you +want installed locally, and its value is the name of the original method +in the class being delegated to. + +This can be very useful for recursive classes like trees. Here is a +quick example (soon to be expanded into a Moose::Cookbook::Recipe): + + package Tree; + use Moose; + + has 'node' => (is => 'rw', isa => 'Any'); + + has 'children' => ( + is => 'ro', + isa => 'ArrayRef', + default => sub { [] } + ); + + has 'parent' => ( + is => 'rw', + isa => 'Tree', + weak_ref => 1, + handles => { + parent_node => 'node', + siblings => 'children', + } + ); + +In this example, the Tree package gets C and C methods, +which delegate to the C and C methods (respectively) of the Tree +instance stored in the C slot. + +=item C + +The regexp option works very similar to the ARRAY option, except that it builds +the list of methods for you. It starts by collecting all possible methods of the +class being delegated to, then filters that list using the regexp supplied here. + +B An I option is required when using the regexp option format. This +is so that we can determine (at compile time) the method list from the class. +Without an I this is just not possible. + +=item C + +With the role option, you specify the name of a role whose "interface" then +becomes the list of methods to handle. The "interface" can be defined as; the +methods of the role and any required methods of the role. It should be noted +that this does B include any method modifiers or generated attribute +methods (which is consistent with role composition). + +=item C + +This is the option to use when you really want to do something funky. You should +only use it if you really know what you are doing, as it involves manual +metaclass twiddling. + +This takes a code reference, which should expect two arguments. The first is the +attribute meta-object this I is attached to. The second is the +metaclass of the class being delegated to. It expects you to return a hash (not +a HASH ref) of the methods you want mapped. + +=back + +=back + +=item B %options> + +This is variation on the normal attibute creator C which allows you to +clone and extend an attribute from a superclass or from a role. Here is an +example of the superclass usage: + + package Foo; + use Moose; + + has 'message' => ( + is => 'rw', + isa => 'Str', + default => 'Hello, I am a Foo' + ); + + package My::Foo; + use Moose; + + extends 'Foo'; + + has '+message' => (default => 'Hello I am My::Foo'); + +What is happening here is that B is cloning the C attribute +from its parent class B, retaining the C 'rw'> and C +'Str'> characteristics, but changing the value in C. + +Here is another example, but within the context of a role: + + package Foo::Role; + use Moose::Role; + + has 'message' => ( + is => 'rw', + isa => 'Str', + default => 'Hello, I am a Foo' + ); + + package My::Foo; + use Moose; + + with 'Foo::Role'; + + has '+message' => (default => 'Hello I am My::Foo'); + +In this case, we are basically taking the attribute which the role supplied +and altering it within the bounds of this feature. -=head1 CODE COVERAGE +Aside from where the attributes come from (one from superclass, the other +from a role), this feature works exactly the same. This feature is restricted +somewhat, so as to try and force at least I sanity into it. You are only +allowed to change the following attributes: -I use L to test the code coverage of my tests, below is the -L report on this module's test suite. +=over 4 + +=item I + +Change the default value of an attribute. + +=item I + +Change whether the attribute attempts to coerce a value passed to it. + +=item I + +Change if the attribute is required to have a value. + +=item I + +Change the documentation string associated with the attribute. + +=item I + +Change if the attribute lazily initializes the slot. + +=item I + +You I allowed to change the type, B the new type is a +subtype of the old type. + +=item I + +You are allowed to B a new C definition, but you are B +allowed to I one. + +=item I + +You are allowed to B a new C definition, but you are B +allowed to I one. + +=back + +=item B sub { ... }> + +=item B sub { ... }> + +=item B sub { ... }> + +This three items are syntactic sugar for the before, after, and around method +modifier features that L provides. More information on these may be +found in the L for now. + +=item B + +The keyword C is a no-op when called outside of an C method. In +the context of an C method, it will call the next most appropriate +superclass method with the same arguments as the original method. + +=item B + +An C method is a way of explicitly saying "I am overriding this +method from my superclass". You can call C within this method, and +it will work as expected. The same thing I be accomplished with a normal +method call and the C pseudo-package; it is really your choice. + +=item B + +The keyword C, much like C, is a no-op outside of the context of +an C method. You can think of C as being the inverse of +C; the details of how C and C work is best described in +the L. + +=item B + +An C method, is a way of explicitly saying "I am augmenting this +method from my superclass". Once again, the details of how C and +C work is best described in the L. + +=item B + +This is the C function, and exported here because I use it +all the time. This feature may change in the future, so you have been warned. + +=item B + +This is the C function, it is exported here because I +use it all the time. It is highly recommended that this is used instead of +C anywhere you need to test for an object's class name. + +=back + +=head1 UNIMPORTING FUNCTIONS + +=head2 B + +Moose offers a way to remove the keywords it exports, through the C +method. You simply have to say C at the bottom of your code for this +to work. Here is an example: + + package Person; + use Moose; + + has 'first_name' => (is => 'rw', isa => 'Str'); + has 'last_name' => (is => 'rw', isa => 'Str'); + + sub full_name { + my $self = shift; + $self->first_name . ' ' . $self->last_name + } + + no Moose; # keywords are removed from the Person package + +=head1 EXTENDING AND EMBEDDING MOOSE + +Moose also offers some options for extending or embedding it into your own +framework. The basic premise is to have something that sets up your class' +metaclass and export the moose declarators (C, C, C,...). +Here is an example: + + package MyFramework; + use Moose; + + sub import { + my $CALLER = caller(); + + strict->import; + warnings->import; + + # we should never export to main + return if $CALLER eq 'main'; + Moose::init_meta( $CALLER, 'MyFramework::Base' ); + Moose->import({into => $CALLER}); + + # Do my custom framework stuff + + return 1; + } + +=head2 B + +Moose's C method supports the L form of C<{into =E $pkg}> +and C<{into_level =E 1}> + +=head2 B + +Moose does some boot strapping: it creates a metaclass object for your class, +and then injects a C accessor into your class to retrieve it. Then it +sets your baseclass to Moose::Object or the value you pass in unless you already +have one. This is all done via C which takes the name of your class +and optionally a baseclass and a metaclass as arguments. + +=head1 CAVEATS + +=over 4 + +=item * + +It should be noted that C and C B be used in the same +method. However, they may be combined within the same class hierarchy; see +F for an example. + +The reason for this is that C is only valid within a method +with the C modifier, and C will never be valid within an +C method. In fact, C will skip over any C methods +when searching for its appropriate C. + +This might seem like a restriction, but I am of the opinion that keeping these +two features separate (yet interoperable) actually makes them easy to use, since +their behavior is then easier to predict. Time will tell whether I am right or +not (UPDATE: so far so good). + +=back =head1 ACKNOWLEDGEMENTS +=over 4 + +=item I blame Sam Vilain for introducing me to the insanity that is meta-models. + +=item I blame Audrey Tang for then encouraging my meta-model habit in #perl6. + +=item Without Yuval "nothingmuch" Kogman this module would not be possible, +and it certainly wouldn't have this name ;P + +=item The basis of the TypeContraints module was Rob Kinyon's idea +originally, I just ran with it. + +=item Thanks to mst & chansen and the whole #moose poose for all the +early ideas/feature-requests/encouragement/bug-finding. + +=item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes. + +=back + +=head1 SEE ALSO + +=over 4 + +=item L + +This is the official web home of Moose, it contains links to our public SVN repo +as well as links to a number of talks and articles on Moose and Moose related +technologies. + +=item L documentation + +=item The #moose channel on irc.perl.org + +=item The Moose mailing list - moose@perl.org + +=item Moose stats on ohloh.net - L + +=item Several Moose extension modules in the L namespace. + +=back + +=head2 Papers + +=over 4 + +=item L + +This paper (suggested by lbr on #moose) was what lead to the implementation +of the C/C and C/C features. If you really +want to understand them, I suggest you read this. + +=back + +=head1 BUGS + +All complex software has bugs lurking in it, and this module is no +exception. If you find a bug please either email me, or add the bug +to cpan-RT. + =head1 AUTHOR Stevan Little Estevan@iinteractive.comE +B + +Aankhen + +Adam (Alias) Kennedy + +Anders (Debolaz) Nor Berle + +Nathan (kolibre) Gray + +Christian (chansen) Hansen + +Hans Dieter (confound) Pearcey + +Eric (ewilhelm) Wilhelm + +Guillermo (groditi) Roditi + +Jess (castaway) Robinson + +Matt (mst) Trout + +Robert (phaylon) Sedlacek + +Robert (rlb3) Boone + +Scott (konobi) McWhirter + +Shlomi (rindolf) Fish + +Yuval (nothingmuch) Kogman + +Chris (perigrin) Prather + +Jonathan (jrockway) Rockway + +Piotr (dexter) Roszatycki + +Sam (mugwump) Vilain + +Shawn (sartak) Moore + +... and many other #moose folks + =head1 COPYRIGHT AND LICENSE -Copyright 2006 by Infinity Interactive, Inc. +Copyright 2006-2008 by Infinity Interactive, Inc. L This library is free software; you can redistribute it and/or modify -it under the same terms as Perl itself. +it under the same terms as Perl itself. -=cut \ No newline at end of file +=cut