--- /dev/null
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
+.\"
+.\" Standard preamble:
+.\" ========================================================================
+.de Sh \" Subsection heading
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Vb \" Begin verbatim text
+.ft CW
+.nf
+.ne \\$1
+..
+.de Ve \" End verbatim text
+.ft R
+.fi
+..
+.\" Set up some character translations and predefined strings. \*(-- will
+.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
+.\" double quote, and \*(R" will give a right double quote. | will give a
+.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
+.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
+.\" expand to `' in nroff, nothing in troff, for use with C<>.
+.tr \(*W-|\(bv\*(Tr
+.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
+.ie n \{\
+. ds -- \(*W-
+. ds PI pi
+. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
+. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
+. ds L" ""
+. ds R" ""
+. ds C` ""
+. ds C' ""
+'br\}
+.el\{\
+. ds -- \|\(em\|
+. ds PI \(*p
+. ds L" ``
+. ds R" ''
+'br\}
+.\"
+.\" If the F register is turned on, we'll generate index entries on stderr for
+.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
+.\" entries marked with X<> in POD. Of course, you'll have to process the
+.\" output yourself in some meaningful fashion.
+.if \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
+..
+. nr % 0
+. rr F
+.\}
+.\"
+.\" For nroff, turn off justification. Always turn off hyphenation; it makes
+.\" way too many mistakes in technical documents.
+.hy 0
+.if n .na
+.\"
+.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
+.\" Fear. Run. Save yourself. No user-serviceable parts.
+. \" fudge factors for nroff and troff
+.if n \{\
+. ds #H 0
+. ds #V .8m
+. ds #F .3m
+. ds #[ \f1
+. ds #] \fP
+.\}
+.if t \{\
+. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
+. ds #V .6m
+. ds #F 0
+. ds #[ \&
+. ds #] \&
+.\}
+. \" simple accents for nroff and troff
+.if n \{\
+. ds ' \&
+. ds ` \&
+. ds ^ \&
+. ds , \&
+. ds ~ ~
+. ds /
+.\}
+.if t \{\
+. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
+. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
+. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
+. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
+. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
+. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
+.\}
+. \" troff and (daisy-wheel) nroff accents
+.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
+.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
+.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
+.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
+.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
+.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
+.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
+.ds ae a\h'-(\w'a'u*4/10)'e
+.ds Ae A\h'-(\w'A'u*4/10)'E
+. \" corrections for vroff
+.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
+.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
+. \" for low resolution devices (crt and lpr)
+.if \n(.H>23 .if \n(.V>19 \
+\{\
+. ds : e
+. ds 8 ss
+. ds o a
+. ds d- d\h'-1'\(ga
+. ds D- D\h'-1'\(hy
+. ds th \o'bp'
+. ds Th \o'LP'
+. ds ae ae
+. ds Ae AE
+.\}
+.rm #[ #] #H #V #F C
+.\" ========================================================================
+.\"
+.IX Title "Class::MOP 3"
+.TH Class::MOP 3 "2009-11-19" "perl v5.8.7" "User Contributed Perl Documentation"
+.SH "NAME"
+Class::MOP \- A Meta Object Protocol for Perl 5
+.SH "DESCRIPTION"
+.IX Header "DESCRIPTION"
+This module is a fully functioning meta object protocol for the
+Perl 5 object system. It makes no attempt to change the behavior or
+characteristics of the Perl 5 object system, only to create a
+protocol for its manipulation and introspection.
+.PP
+That said, it does attempt to create the tools for building a rich set
+of extensions to the Perl 5 object system. Every attempt has been made
+to abide by the spirit of the Perl 5 object system that we all know
+and love.
+.PP
+This documentation is sparse on conceptual details. We suggest looking
+at the items listed in the \*(L"\s-1SEE\s0 \s-1ALSO\s0\*(R" section for more
+information. In particular the book \*(L"The Art of the Meta Object
+Protocol\*(R" was very influential in the development of this system.
+.Sh "What is a Meta Object Protocol?"
+.IX Subsection "What is a Meta Object Protocol?"
+A meta object protocol is an \s-1API\s0 to an object system.
+.PP
+To be more specific, it abstracts the components of an object system
+(classes, object, methods, object attributes, etc.). These
+abstractions can then be used to inspect and manipulate the object
+system which they describe.
+.PP
+It can be said that there are two MOPs for any object system; the
+implicit \s-1MOP\s0 and the explicit \s-1MOP\s0. The implicit \s-1MOP\s0 handles things
+like method dispatch or inheritance, which happen automatically as
+part of how the object system works. The explicit \s-1MOP\s0 typically
+handles the introspection/reflection features of the object system.
+.PP
+All object systems have implicit MOPs. Without one, they would not
+work. Explicit MOPs are much less common, and depending on the
+language can vary from restrictive (Reflection in Java or C#) to wide
+open (\s-1CLOS\s0 is a perfect example).
+.Sh "Yet Another Class Builder! Why?"
+.IX Subsection "Yet Another Class Builder! Why?"
+This is \fBnot\fR a class builder so much as a \fIclass builder
+\&\f(BIbuilder\fI\fR. The intent is that an end user will not use this module
+directly, but instead this module is used by module authors to build
+extensions and features onto the Perl 5 object system.
+.PP
+This system is used by Moose, which supplies a powerful class
+builder system built entirely on top of \f(CW\*(C`Class::MOP\*(C'\fR.
+.Sh "Who is this module for?"
+.IX Subsection "Who is this module for?"
+This module is for anyone who has ever created or wanted to create a
+module for the Class:: namespace. The tools which this module provides
+make doing complex Perl 5 wizardry simpler, by removing such barriers
+as the need to hack symbol tables, or understand the fine details of
+method dispatch.
+.Sh "What changes do I have to make to use this module?"
+.IX Subsection "What changes do I have to make to use this module?"
+This module was designed to be as unintrusive as possible. Many of its
+features are accessible without \fBany\fR change to your existing
+code. It is meant to be a compliment to your existing code and not an
+intrusion on your code base. Unlike many other \fBClass::\fR modules,
+this module \fBdoes not\fR require you subclass it, or even that you
+\&\f(CW\*(C`use\*(C'\fR it in within your module's package.
+.PP
+The only features which requires additions to your code are the
+attribute handling and instance construction features, and these are
+both completely optional features. The only reason for this is because
+Perl 5's object system does not actually have these features built
+in. More information about this feature can be found below.
+.Sh "About Performance"
+.IX Subsection "About Performance"
+It is a common misconception that explicit MOPs are a performance hit.
+This is not a universal truth, it is a side-effect of some specific
+implementations. For instance, using Java reflection is slow because
+the \s-1JVM\s0 cannot take advantage of any compiler optimizations, and the
+\&\s-1JVM\s0 has to deal with much more runtime type information as well.
+.PP
+Reflection in C# is marginally better as it was designed into the
+language and runtime (the \s-1CLR\s0). In contrast, \s-1CLOS\s0 (the Common Lisp
+Object System) was built to support an explicit \s-1MOP\s0, and so
+performance is tuned for it.
+.PP
+This library in particular does its absolute best to avoid putting
+\&\fBany\fR drain at all upon your code's performance. In fact, by itself
+it does nothing to affect your existing code. So you only pay for what
+you actually use.
+.Sh "About Metaclass compatibility"
+.IX Subsection "About Metaclass compatibility"
+This module makes sure that all metaclasses created are both upwards
+and downwards compatible. The topic of metaclass compatibility is
+highly esoteric and is something only encountered when doing deep and
+involved metaclass hacking. There are two basic kinds of metaclass
+incompatibility; upwards and downwards.
+.PP
+Upwards metaclass compatibility means that the metaclass of a
+given class is either the same as (or a subclass of) all of the
+class's ancestors.
+.PP
+Downward metaclass compatibility means that the metaclasses of a
+given class's ancestors are all either the same as (or a subclass
+of) that metaclass.
+.PP
+Here is a diagram showing a set of two classes (\f(CW\*(C`A\*(C'\fR and \f(CW\*(C`B\*(C'\fR) and
+two metaclasses (\f(CW\*(C`Meta::A\*(C'\fR and \f(CW\*(C`Meta::B\*(C'\fR) which have correct
+metaclass compatibility both upwards and downwards.
+.PP
+.Vb 8
+\& +\-\-\-\-\-\-\-\-\-+ +\-\-\-\-\-\-\-\-\-+
+\& | Meta::A |<\-\-\-\-| Meta::B | <....... (instance of )
+\& +\-\-\-\-\-\-\-\-\-+ +\-\-\-\-\-\-\-\-\-+ <\-\-\-\-\-\-\- (inherits from)
+\& ^ ^
+\& : :
+\& +\-\-\-\-\-\-\-\-\-+ +\-\-\-\-\-\-\-\-\-+
+\& | A |<\-\-\-\-| B |
+\& +\-\-\-\-\-\-\-\-\-+ +\-\-\-\-\-\-\-\-\-+
+.Ve
+.PP
+As I said this is a highly esoteric topic and one you will only run
+into if you do a lot of subclassing of Class::MOP::Class. If you
+are interested in why this is an issue see the paper \fIUniform and
+safe metaclass composition\fR linked to in the \*(L"\s-1SEE\s0 \s-1ALSO\s0\*(R" section of
+this document.
+.Sh "Using custom metaclasses"
+.IX Subsection "Using custom metaclasses"
+Always use the metaclass pragma when using a custom metaclass, this
+will ensure the proper initialization order and not accidentally
+create an incorrect type of metaclass for you. This is a very rare
+problem, and one which can only occur if you are doing deep metaclass
+programming. So in other words, don't worry about it.
+.PP
+Note that if you're using Moose we encourage you to \fInot\fR use
+metaclass pragma, and instead use Moose::Util::MetaRole to apply
+roles to a class's metaclasses. This topic is covered at length in
+various Moose::Cookbook recipes.
+.SH "PROTOCOLS"
+.IX Header "PROTOCOLS"
+The meta-object protocol is divided into 4 main sub\-protocols:
+.Sh "The Class protocol"
+.IX Subsection "The Class protocol"
+This provides a means of manipulating and introspecting a Perl 5
+class. It handles symbol table hacking for you, and provides a rich
+set of methods that go beyond simple package introspection.
+.PP
+See Class::MOP::Class for more details.
+.Sh "The Attribute protocol"
+.IX Subsection "The Attribute protocol"
+This provides a consistent representation for an attribute of a Perl 5
+class. Since there are so many ways to create and handle attributes in
+Perl 5 \s-1OO\s0, the Attribute protocol provide as much of a unified
+approach as possible. Of course, you are always free to extend this
+protocol by subclassing the appropriate classes.
+.PP
+See Class::MOP::Attribute for more details.
+.Sh "The Method protocol"
+.IX Subsection "The Method protocol"
+This provides a means of manipulating and introspecting methods in the
+Perl 5 object system. As with attributes, there are many ways to
+approach this topic, so we try to keep it pretty basic, while still
+making it possible to extend the system in many ways.
+.PP
+See Class::MOP::Method for more details.
+.Sh "The Instance protocol"
+.IX Subsection "The Instance protocol"
+This provides a layer of abstraction for creating object instances.
+Since the other layers use this protocol, it is relatively easy to
+change the type of your instances from the default hash reference to
+some other type of reference. Several examples are provided in the
+\&\fIexamples/\fR directory included in this distribution.
+.PP
+See Class::MOP::Instance for more details.
+.SH "FUNCTIONS"
+.IX Header "FUNCTIONS"
+Note that this module does not export any constants or functions.
+.Sh "Constants"
+.IX Subsection "Constants"
+.IP "\fIClass::MOP::IS_RUNNING_ON_5_10\fR" 4
+.IX Item "Class::MOP::IS_RUNNING_ON_5_10"
+We set this constant depending on what version perl we are on, this
+allows us to take advantage of new 5.10 features and stay backwards
+compatible.
+.Sh "Utility functions"
+.IX Subsection "Utility functions"
+Note that these are all called as \fBfunctions, not methods\fR.
+.IP "\fBClass::MOP::load_class($class_name)\fR" 4
+.IX Item "Class::MOP::load_class($class_name)"
+This will load the specified \f(CW$class_name\fR, if it is not already
+loaded (as reported by \f(CW\*(C`is_class_loaded\*(C'\fR). This function can be used
+in place of tricks like \f(CW\*(C`eval "use $module"\*(C'\fR or using \f(CW\*(C`require\*(C'\fR
+unconditionally.
+.Sp
+If the module cannot be loaded, an exception is thrown.
+.Sp
+For historical reasons, this function explicitly returns a true value.
+.IP "\fBClass::MOP::is_class_loaded($class_name)\fR" 4
+.IX Item "Class::MOP::is_class_loaded($class_name)"
+Returns a boolean indicating whether or not \f(CW$class_name\fR has been
+loaded.
+.Sp
+This does a basic check of the symbol table to try and determine as
+best it can if the \f(CW$class_name\fR is loaded, it is probably correct
+about 99% of the time, but it can be fooled into reporting false
+positives. In particular, loading any of the core \s-1IO\s0 modules will
+cause most of the rest of the core \s-1IO\s0 modules to falsely report
+having been loaded, due to the way the base \s-1IO\s0 module works.
+.IP "\fBClass::MOP::get_code_info($code)\fR" 4
+.IX Item "Class::MOP::get_code_info($code)"
+This function returns two values, the name of the package the \f(CW$code\fR
+is from and the name of the \f(CW$code\fR itself. This is used by several
+elements of the \s-1MOP\s0 to determine where a given \f(CW$code\fR reference is
+from.
+.IP "\fBClass::MOP::class_of($instance_or_class_name)\fR" 4
+.IX Item "Class::MOP::class_of($instance_or_class_name)"
+This will return the metaclass of the given instance or class name. If the
+class lacks a metaclass, no metaclass will be initialized, and \f(CW\*(C`undef\*(C'\fR will be
+returned.
+.IP "\fBClass::MOP::check_package_cache_flag($pkg)\fR" 4
+.IX Item "Class::MOP::check_package_cache_flag($pkg)"
+\&\fB\s-1NOTE:\s0 \s-1DO\s0 \s-1NOT\s0 \s-1USE\s0 \s-1THIS\s0 \s-1FUNCTION\s0, \s-1IT\s0 \s-1IS\s0 \s-1FOR\s0 \s-1INTERNAL\s0 \s-1USE\s0 \s-1ONLY\s0!\fR
+.Sp
+This will return an integer that is managed by Class::MOP::Class to
+determine if a module's symbol table has been altered.
+.Sp
+In Perl 5.10 or greater, this flag is package specific. However in
+versions prior to 5.10, this will use the \f(CW\*(C`PL_sub_generation\*(C'\fR
+variable which is not package specific.
+.IP "\fBClass::MOP::load_first_existing_class(@class_names)\fR" 4
+.IX Item "Class::MOP::load_first_existing_class(@class_names)"
+\&\fB\s-1NOTE:\s0 \s-1DO\s0 \s-1NOT\s0 \s-1USE\s0 \s-1THIS\s0 \s-1FUNCTION\s0, \s-1IT\s0 \s-1IS\s0 \s-1FOR\s0 \s-1INTERNAL\s0 \s-1USE\s0 \s-1ONLY\s0!\fR
+.Sp
+Given a list of class names, this function will attempt to load each
+one in turn.
+.Sp
+If it finds a class it can load, it will return that class' name. If
+none of the classes can be loaded, it will throw an exception.
+.Sh "Metaclass cache functions"
+.IX Subsection "Metaclass cache functions"
+Class::MOP holds a cache of metaclasses. The following are functions
+(\fBnot methods\fR) which can be used to access that cache. It is not
+recommended that you mess with these. Bad things could happen, but if
+you are brave and willing to risk it: go for it!
+.IP "\fBClass::MOP::get_all_metaclasses\fR" 4
+.IX Item "Class::MOP::get_all_metaclasses"
+This will return a hash of all the metaclass instances that have
+been cached by Class::MOP::Class, keyed by the package name.
+.IP "\fBClass::MOP::get_all_metaclass_instances\fR" 4
+.IX Item "Class::MOP::get_all_metaclass_instances"
+This will return a list of all the metaclass instances that have
+been cached by Class::MOP::Class.
+.IP "\fBClass::MOP::get_all_metaclass_names\fR" 4
+.IX Item "Class::MOP::get_all_metaclass_names"
+This will return a list of all the metaclass names that have
+been cached by Class::MOP::Class.
+.IP "\fBClass::MOP::get_metaclass_by_name($name)\fR" 4
+.IX Item "Class::MOP::get_metaclass_by_name($name)"
+This will return a cached Class::MOP::Class instance, or nothing
+if no metaclass exists with that \f(CW$name\fR.
+.ie n .IP "\fBClass::MOP::store_metaclass_by_name($name, \fB$meta\fB)\fR" 4
+.el .IP "\fBClass::MOP::store_metaclass_by_name($name, \f(CB$meta\fB)\fR" 4
+.IX Item "Class::MOP::store_metaclass_by_name($name, $meta)"
+This will store a metaclass in the cache at the supplied \f(CW$key\fR.
+.IP "\fBClass::MOP::weaken_metaclass($name)\fR" 4
+.IX Item "Class::MOP::weaken_metaclass($name)"
+In rare cases (e.g. anonymous metaclasses) it is desirable to
+store a weakened reference in the metaclass cache. This
+function will weaken the reference to the metaclass stored
+in \f(CW$name\fR.
+.IP "\fBClass::MOP::does_metaclass_exist($name)\fR" 4
+.IX Item "Class::MOP::does_metaclass_exist($name)"
+This will return true of there exists a metaclass stored in the
+\&\f(CW$name\fR key, and return false otherwise.
+.IP "\fBClass::MOP::remove_metaclass_by_name($name)\fR" 4
+.IX Item "Class::MOP::remove_metaclass_by_name($name)"
+This will remove the metaclass stored in the \f(CW$name\fR key.
+.SH "SEE ALSO"
+.IX Header "SEE ALSO"
+.Sh "Books"
+.IX Subsection "Books"
+There are very few books out on Meta Object Protocols and Metaclasses
+because it is such an esoteric topic. The following books are really
+the only ones I have found. If you know of any more, \fB\f(BIplease\fB\fR
+email me and let me know, I would love to hear about them.
+.IP "\fIThe Art of the Meta Object Protocol\fR" 4
+.IX Item "The Art of the Meta Object Protocol"
+.PD 0
+.IP "\fIAdvances in Object-Oriented Metalevel Architecture and Reflection\fR" 4
+.IX Item "Advances in Object-Oriented Metalevel Architecture and Reflection"
+.IP "\fIPutting MetaClasses to Work\fR" 4
+.IX Item "Putting MetaClasses to Work"
+.IP "\fISmalltalk: The Language\fR" 4
+.IX Item "Smalltalk: The Language"
+.PD
+.Sh "Papers"
+.IX Subsection "Papers"
+.ie n .IP """Uniform and safe metaclass composition""" 4
+.el .IP "``Uniform and safe metaclass composition''" 4
+.IX Item "Uniform and safe metaclass composition"
+An excellent paper by the people who brought us the original Traits paper.
+This paper is on how Traits can be used to do safe metaclass composition,
+and offers an excellent introduction section which delves into the topic of
+metaclass compatibility.
+.Sp
+<http://www.iam.unibe.ch/~scg/Archive/Papers/Duca05ySafeMetaclassTrait.pdf>
+.ie n .IP """Safe Metaclass Programming""" 4
+.el .IP "``Safe Metaclass Programming''" 4
+.IX Item "Safe Metaclass Programming"
+This paper seems to precede the above paper, and propose a mix-in based
+approach as opposed to the Traits based approach. Both papers have similar
+information on the metaclass compatibility problem space.
+.Sp
+<http://citeseer.ist.psu.edu/37617.html>
+.Sh "Prior Art"
+.IX Subsection "Prior Art"
+.IP "The Perl 6 MetaModel work in the Pugs project" 4
+.IX Item "The Perl 6 MetaModel work in the Pugs project"
+.RS 4
+.PD 0
+.IP "<http://svn.openfoundry.org/pugs/misc/Perl\-MetaModel/>" 4
+.IX Item "<http://svn.openfoundry.org/pugs/misc/Perl-MetaModel/>"
+.IP "<http://svn.openfoundry.org/pugs/perl5/Perl6\-ObjectSpace>" 4
+.IX Item "<http://svn.openfoundry.org/pugs/perl5/Perl6-ObjectSpace>"
+.RE
+.RS 4
+.RE
+.PD
+.Sh "Articles"
+.IX Subsection "Articles"
+.IP "\s-1CPAN\s0 Module Review of Class::MOP" 4
+.IX Item "CPAN Module Review of Class::MOP"
+<http://www.oreillynet.com/onlamp/blog/2006/06/cpan_module_review_classmop.html>
+.SH "SIMILAR MODULES"
+.IX Header "SIMILAR MODULES"
+As I have said above, this module is a class\-builder\-builder, so it is
+not the same thing as modules like Class::Accessor and
+Class::MethodMaker. That being said there are very few modules on \s-1CPAN\s0
+with similar goals to this module. The one I have found which is most
+like this module is Class::Meta, although it's philosophy and the \s-1MOP\s0 it
+creates are very different from this modules.
+.SH "BUGS"
+.IX Header "BUGS"
+All complex software has bugs lurking in it, and this module is no
+exception.
+.PP
+Please report any bugs to \f(CW\*(C`bug\-class\-mop@rt.cpan.org\*(C'\fR, or through the
+web interface at <http://rt.cpan.org>.
+.PP
+You can also discuss feature requests or possible bugs on the Moose
+mailing list (moose@perl.org) or on \s-1IRC\s0 at
+<irc://irc.perl.org/#moose>.
+.SH "ACKNOWLEDGEMENTS"
+.IX Header "ACKNOWLEDGEMENTS"
+.IP "Rob Kinyon" 4
+.IX Item "Rob Kinyon"
+Thanks to Rob for actually getting the development of this module kick\-started.
+.SH "AUTHORS"
+.IX Header "AUTHORS"
+Stevan Little <stevan@iinteractive.com>
+.PP
+\&\fBwith contributions from:\fR
+.PP
+Brandon (blblack) Black
+.PP
+Florian (rafl) Ragwitz
+.PP
+Guillermo (groditi) Roditi
+.PP
+Dave (autarch) Rolsky
+.PP
+Matt (mst) Trout
+.PP
+Rob (robkinyon) Kinyon
+.PP
+Yuval (nothingmuch) Kogman
+.PP
+Scott (konobi) McWhirter
+.PP
+Dylan Hardison
+.SH "COPYRIGHT AND LICENSE"
+.IX Header "COPYRIGHT AND LICENSE"
+Copyright 2006\-2009 by Infinity Interactive, Inc.
+.PP
+<http://www.iinteractive.com>
+.PP
+This library is free software; you can redistribute it and/or modify
+it under the same terms as Perl itself.
projects / catagits/Gitalist.git / blobdiff