10 use Scalar::Util 'weaken';
12 use Sub::Identify 'get_code_info';
18 Sub::Name->import(qw(subname));
20 } or eval 'sub subname { $_[1] }';
22 # this is either part of core or set up appropriately by MRO::Compat
23 *check_package_cache_flag = \&mro::get_pkg_gen;
26 require Devel::GlobalDestruction;
27 Devel::GlobalDestruction->import("in_global_destruction");
29 } or *in_global_destruction = sub () { '' };
33 use Class::MOP::Class;
34 use Class::MOP::Attribute;
35 use Class::MOP::Method;
37 use Class::MOP::Immutable;
40 *IS_RUNNING_ON_5_10 = ($] < 5.009_005)
44 *HAVE_ISAREV = defined(&mro::get_isarev)
49 our $VERSION = '0.65';
50 our $AUTHORITY = 'cpan:STEVAN';
52 # after that everything is loaded, if we're allowed try to load faster XS
53 # versions of various things
54 unless ($ENV{CLASS_MOP_NO_XS}) {
59 __PACKAGE__->XSLoader::load($VERSION);
64 die $e if $e && $e !~ /object version|loadable object/;
68 # Metaclasses are singletons, so we cache them here.
69 # there is no need to worry about destruction though
70 # because they should die only when the program dies.
71 # After all, do package definitions even get reaped?
74 # means of accessing all the metaclasses that have
75 # been initialized thus far (for mugwumps obj browser)
76 sub get_all_metaclasses { %METAS }
77 sub get_all_metaclass_instances { values %METAS }
78 sub get_all_metaclass_names { keys %METAS }
79 sub get_metaclass_by_name { $METAS{$_[0]} }
80 sub store_metaclass_by_name { $METAS{$_[0]} = $_[1] }
81 sub weaken_metaclass { weaken($METAS{$_[0]}) }
82 sub does_metaclass_exist { exists $METAS{$_[0]} && defined $METAS{$_[0]} }
83 sub remove_metaclass_by_name { $METAS{$_[0]} = undef }
86 # We only cache metaclasses, meaning instances of
87 # Class::MOP::Class. We do not cache instance of
88 # Class::MOP::Package or Class::MOP::Module. Mostly
89 # because I don't yet see a good reason to do so.
95 if (ref($class) || !defined($class) || !length($class)) {
96 my $display = defined($class) ? $class : 'undef';
97 confess "Invalid class name ($display)";
100 # if the class is not already loaded in the symbol table..
101 unless (is_class_loaded($class)) {
103 my $file = $class . '.pm';
105 my $e = do { local $@; eval { require($file) }; $@ };
106 confess "Could not load class ($class) because : $e" if $e;
109 # initialize a metaclass if necessary
110 unless (does_metaclass_exist($class)) {
111 my $e = do { local $@; eval { Class::MOP::Class->initialize($class) }; $@ };
112 confess "Could not initialize class ($class) because : $e" if $e;
115 return get_metaclass_by_name($class) if defined wantarray;
118 sub is_class_loaded {
121 return 0 if ref($class) || !defined($class) || !length($class);
123 # walk the symbol table tree to avoid autovififying
124 # \*{${main::}{"Foo::"}} == \*main::Foo::
127 foreach my $part (split('::', $class)) {
128 return 0 unless exists ${$$pack}{"${part}::"};
129 $pack = \*{${$$pack}{"${part}::"}};
132 # check for $VERSION or @ISA
133 return 1 if exists ${$$pack}{VERSION}
134 && defined *{${$$pack}{VERSION}}{SCALAR};
135 return 1 if exists ${$$pack}{ISA}
136 && defined *{${$$pack}{ISA}}{ARRAY};
138 # check for any method
139 foreach ( keys %{$$pack} ) {
140 next if substr($_, -2, 2) eq '::';
142 my $glob = ${$$pack}{$_} || next;
145 if ( IS_RUNNING_ON_5_10 ) {
146 return 1 if ref $glob eq 'SCALAR';
149 return 1 if defined *{$glob}{CODE};
157 ## ----------------------------------------------------------------------------
158 ## Setting up our environment ...
159 ## ----------------------------------------------------------------------------
160 ## Class::MOP needs to have a few things in the global perl environment so
161 ## that it can operate effectively. Those things are done here.
162 ## ----------------------------------------------------------------------------
164 # ... nothing yet actually ;)
166 ## ----------------------------------------------------------------------------
168 ## ----------------------------------------------------------------------------
169 ## The code below here is to bootstrap our MOP with itself. This is also
170 ## sometimes called "tying the knot". By doing this, we make it much easier
171 ## to extend the MOP through subclassing and such since now you can use the
172 ## MOP itself to extend itself.
174 ## Yes, I know, thats weird and insane, but it's a good thing, trust me :)
175 ## ----------------------------------------------------------------------------
177 # We need to add in the meta-attributes here so that
178 # any subclass of Class::MOP::* will be able to
179 # inherit them using &construct_instance
181 ## --------------------------------------------------------
182 ## Class::MOP::Package
184 Class::MOP::Package->meta->add_attribute(
185 Class::MOP::Attribute->new('package' => (
187 # NOTE: we need to do this in order
188 # for the instance meta-object to
189 # not fall into meta-circular death
191 # we just alias the original method
192 # rather than re-produce it here
193 'name' => \&Class::MOP::Package::name
198 Class::MOP::Package->meta->add_attribute(
199 Class::MOP::Attribute->new('namespace' => (
202 # we just alias the original method
203 # rather than re-produce it here
204 'namespace' => \&Class::MOP::Package::namespace
207 default => sub { \undef }
211 ## --------------------------------------------------------
212 ## Class::MOP::Module
215 # yeah this is kind of stretching things a bit,
216 # but truthfully the version should be an attribute
217 # of the Module, the weirdness comes from having to
218 # stick to Perl 5 convention and store it in the
219 # $VERSION package variable. Basically if you just
220 # squint at it, it will look how you want it to look.
221 # Either as a package variable, or as a attribute of
222 # the metaclass, isn't abstraction great :)
224 Class::MOP::Module->meta->add_attribute(
225 Class::MOP::Attribute->new('version' => (
228 # we just alias the original method
229 # rather than re-produce it here
230 'version' => \&Class::MOP::Module::version
233 default => sub { \undef }
238 # By following the same conventions as version here,
239 # we are opening up the possibility that people can
240 # use the $AUTHORITY in non-Class::MOP modules as
243 Class::MOP::Module->meta->add_attribute(
244 Class::MOP::Attribute->new('authority' => (
247 # we just alias the original method
248 # rather than re-produce it here
249 'authority' => \&Class::MOP::Module::authority
252 default => sub { \undef }
256 ## --------------------------------------------------------
259 Class::MOP::Class->meta->add_attribute(
260 Class::MOP::Attribute->new('attributes' => (
262 # NOTE: we need to do this in order
263 # for the instance meta-object to
264 # not fall into meta-circular death
266 # we just alias the original method
267 # rather than re-produce it here
268 'get_attribute_map' => \&Class::MOP::Class::get_attribute_map
270 default => sub { {} }
274 Class::MOP::Class->meta->add_attribute(
275 Class::MOP::Attribute->new('methods' => (
278 # we just alias the original method
279 # rather than re-produce it here
280 'get_method_map' => \&Class::MOP::Class::get_method_map
282 default => sub { {} }
286 Class::MOP::Class->meta->add_attribute(
287 Class::MOP::Attribute->new('superclasses' => (
290 # we just alias the original method
291 # rather than re-produce it here
292 'superclasses' => \&Class::MOP::Class::superclasses
295 default => sub { \undef }
299 Class::MOP::Class->meta->add_attribute(
300 Class::MOP::Attribute->new('attribute_metaclass' => (
303 # we just alias the original method
304 # rather than re-produce it here
305 'attribute_metaclass' => \&Class::MOP::Class::attribute_metaclass
307 default => 'Class::MOP::Attribute',
311 Class::MOP::Class->meta->add_attribute(
312 Class::MOP::Attribute->new('method_metaclass' => (
315 # we just alias the original method
316 # rather than re-produce it here
317 'method_metaclass' => \&Class::MOP::Class::method_metaclass
319 default => 'Class::MOP::Method',
323 Class::MOP::Class->meta->add_attribute(
324 Class::MOP::Attribute->new('instance_metaclass' => (
326 # NOTE: we need to do this in order
327 # for the instance meta-object to
328 # not fall into meta-circular death
330 # we just alias the original method
331 # rather than re-produce it here
332 'instance_metaclass' => \&Class::MOP::Class::instance_metaclass
334 default => 'Class::MOP::Instance',
339 # we don't actually need to tie the knot with
340 # Class::MOP::Class here, it is actually handled
341 # within Class::MOP::Class itself in the
342 # construct_class_instance method.
344 ## --------------------------------------------------------
345 ## Class::MOP::Attribute
347 Class::MOP::Attribute->meta->add_attribute(
348 Class::MOP::Attribute->new('name' => (
350 # NOTE: we need to do this in order
351 # for the instance meta-object to
352 # not fall into meta-circular death
354 # we just alias the original method
355 # rather than re-produce it here
356 'name' => \&Class::MOP::Attribute::name
361 Class::MOP::Attribute->meta->add_attribute(
362 Class::MOP::Attribute->new('associated_class' => (
364 # NOTE: we need to do this in order
365 # for the instance meta-object to
366 # not fall into meta-circular death
368 # we just alias the original method
369 # rather than re-produce it here
370 'associated_class' => \&Class::MOP::Attribute::associated_class
375 Class::MOP::Attribute->meta->add_attribute(
376 Class::MOP::Attribute->new('accessor' => (
377 reader => { 'accessor' => \&Class::MOP::Attribute::accessor },
378 predicate => { 'has_accessor' => \&Class::MOP::Attribute::has_accessor },
382 Class::MOP::Attribute->meta->add_attribute(
383 Class::MOP::Attribute->new('reader' => (
384 reader => { 'reader' => \&Class::MOP::Attribute::reader },
385 predicate => { 'has_reader' => \&Class::MOP::Attribute::has_reader },
389 Class::MOP::Attribute->meta->add_attribute(
390 Class::MOP::Attribute->new('initializer' => (
391 reader => { 'initializer' => \&Class::MOP::Attribute::initializer },
392 predicate => { 'has_initializer' => \&Class::MOP::Attribute::has_initializer },
396 Class::MOP::Attribute->meta->add_attribute(
397 Class::MOP::Attribute->new('writer' => (
398 reader => { 'writer' => \&Class::MOP::Attribute::writer },
399 predicate => { 'has_writer' => \&Class::MOP::Attribute::has_writer },
403 Class::MOP::Attribute->meta->add_attribute(
404 Class::MOP::Attribute->new('predicate' => (
405 reader => { 'predicate' => \&Class::MOP::Attribute::predicate },
406 predicate => { 'has_predicate' => \&Class::MOP::Attribute::has_predicate },
410 Class::MOP::Attribute->meta->add_attribute(
411 Class::MOP::Attribute->new('clearer' => (
412 reader => { 'clearer' => \&Class::MOP::Attribute::clearer },
413 predicate => { 'has_clearer' => \&Class::MOP::Attribute::has_clearer },
417 Class::MOP::Attribute->meta->add_attribute(
418 Class::MOP::Attribute->new('builder' => (
419 reader => { 'builder' => \&Class::MOP::Attribute::builder },
420 predicate => { 'has_builder' => \&Class::MOP::Attribute::has_builder },
424 Class::MOP::Attribute->meta->add_attribute(
425 Class::MOP::Attribute->new('init_arg' => (
426 reader => { 'init_arg' => \&Class::MOP::Attribute::init_arg },
427 predicate => { 'has_init_arg' => \&Class::MOP::Attribute::has_init_arg },
431 Class::MOP::Attribute->meta->add_attribute(
432 Class::MOP::Attribute->new('default' => (
433 # default has a custom 'reader' method ...
434 predicate => { 'has_default' => \&Class::MOP::Attribute::has_default },
438 Class::MOP::Attribute->meta->add_attribute(
439 Class::MOP::Attribute->new('associated_methods' => (
440 reader => { 'associated_methods' => \&Class::MOP::Attribute::associated_methods },
441 default => sub { [] }
445 Class::MOP::Attribute->meta->add_method('clone' => sub {
447 $self->meta->clone_object($self, @_);
450 ## --------------------------------------------------------
451 ## Class::MOP::Method
452 Class::MOP::Method->meta->add_attribute(
453 Class::MOP::Attribute->new('body' => (
454 reader => { 'body' => \&Class::MOP::Method::body },
458 Class::MOP::Method->meta->add_attribute(
459 Class::MOP::Attribute->new('associated_metaclass' => (
460 reader => { 'associated_metaclass' => \&Class::MOP::Method::associated_metaclass },
464 Class::MOP::Method->meta->add_attribute(
465 Class::MOP::Attribute->new('package_name' => (
466 reader => { 'package_name' => \&Class::MOP::Method::package_name },
470 Class::MOP::Method->meta->add_attribute(
471 Class::MOP::Attribute->new('name' => (
472 reader => { 'name' => \&Class::MOP::Method::name },
476 Class::MOP::Method->meta->add_method('clone' => sub {
478 $self->meta->clone_object($self, @_);
481 ## --------------------------------------------------------
482 ## Class::MOP::Method::Wrapped
485 # the way this item is initialized, this
486 # really does not follow the standard
487 # practices of attributes, but we put
488 # it here for completeness
489 Class::MOP::Method::Wrapped->meta->add_attribute(
490 Class::MOP::Attribute->new('modifier_table')
493 ## --------------------------------------------------------
494 ## Class::MOP::Method::Generated
496 Class::MOP::Method::Generated->meta->add_attribute(
497 Class::MOP::Attribute->new('is_inline' => (
498 reader => { 'is_inline' => \&Class::MOP::Method::Generated::is_inline },
503 ## --------------------------------------------------------
504 ## Class::MOP::Method::Accessor
506 Class::MOP::Method::Accessor->meta->add_attribute(
507 Class::MOP::Attribute->new('attribute' => (
509 'associated_attribute' => \&Class::MOP::Method::Accessor::associated_attribute
514 Class::MOP::Method::Accessor->meta->add_attribute(
515 Class::MOP::Attribute->new('accessor_type' => (
516 reader => { 'accessor_type' => \&Class::MOP::Method::Accessor::accessor_type },
520 ## --------------------------------------------------------
521 ## Class::MOP::Method::Constructor
523 Class::MOP::Method::Constructor->meta->add_attribute(
524 Class::MOP::Attribute->new('options' => (
526 'options' => \&Class::MOP::Method::Constructor::options
528 default => sub { +{} }
532 Class::MOP::Method::Constructor->meta->add_attribute(
533 Class::MOP::Attribute->new('associated_metaclass' => (
534 init_arg => "metaclass", # FIXME alias and rename
536 'associated_metaclass' => \&Class::MOP::Method::Constructor::associated_metaclass
541 ## --------------------------------------------------------
542 ## Class::MOP::Instance
545 # these don't yet do much of anything, but are just
546 # included for completeness
548 Class::MOP::Instance->meta->add_attribute(
549 Class::MOP::Attribute->new('associated_metaclass',
550 reader => { associated_metaclass => \&Class::MOP::Instance::associated_metaclass },
554 Class::MOP::Instance->meta->add_attribute(
555 Class::MOP::Attribute->new('_class_name',
557 reader => { _class_name => \&Class::MOP::Instance::_class_name },
558 #lazy => 1, # not yet supported by Class::MOP but out our version does it anyway
559 #default => sub { $_[0]->associated_metaclass->name },
563 Class::MOP::Instance->meta->add_attribute(
564 Class::MOP::Attribute->new('attributes',
565 reader => { attributes => \&Class::MOP::Instance::attributes },
569 Class::MOP::Instance->meta->add_attribute(
570 Class::MOP::Attribute->new('slots',
571 reader => { slots => \&Class::MOP::Instance::slots },
575 Class::MOP::Instance->meta->add_attribute(
576 Class::MOP::Attribute->new('slot_hash',
577 reader => { slot_hash => \&Class::MOP::Instance::slot_hash },
582 # we need the meta instance of the meta instance to be created now, in order
583 # for the constructor to be able to use it
584 Class::MOP::Instance->meta->get_meta_instance;
586 # pretend the add_method never happenned. it hasn't yet affected anything
587 undef Class::MOP::Instance->meta->{_package_cache_flag};
589 ## --------------------------------------------------------
590 ## Now close all the Class::MOP::* classes
593 # we don't need to inline the
594 # constructors or the accessors
595 # this only lengthens the compile
596 # time of the MOP, and gives us
597 # no actual benefits.
599 $_->meta->make_immutable(
600 inline_constructor => 1,
601 replace_constructor => 1,
602 constructor_name => "_new",
603 inline_accessors => 0,
609 Class::MOP::Attribute
615 Class::MOP::Method::Generated
617 Class::MOP::Method::Accessor
618 Class::MOP::Method::Constructor
619 Class::MOP::Method::Wrapped
630 Class::MOP - A Meta Object Protocol for Perl 5
634 This module is a fully functioning meta object protocol for the
635 Perl 5 object system. It makes no attempt to change the behavior or
636 characteristics of the Perl 5 object system, only to create a
637 protocol for its manipulation and introspection.
639 That said, it does attempt to create the tools for building a rich
640 set of extensions to the Perl 5 object system. Every attempt has been
641 made for these tools to keep to the spirit of the Perl 5 object
642 system that we all know and love.
644 This documentation is admittedly sparse on details, as time permits
645 I will try to improve them. For now, I suggest looking at the items
646 listed in the L<SEE ALSO> section for more information. In particular
647 the book "The Art of the Meta Object Protocol" was very influential
648 in the development of this system.
650 =head2 What is a Meta Object Protocol?
652 A meta object protocol is an API to an object system.
654 To be more specific, it is a set of abstractions of the components of
655 an object system (typically things like; classes, object, methods,
656 object attributes, etc.). These abstractions can then be used to both
657 inspect and manipulate the object system which they describe.
659 It can be said that there are two MOPs for any object system; the
660 implicit MOP, and the explicit MOP. The implicit MOP handles things
661 like method dispatch or inheritance, which happen automatically as
662 part of how the object system works. The explicit MOP typically
663 handles the introspection/reflection features of the object system.
664 All object systems have implicit MOPs, without one, they would not
665 work. Explict MOPs however as less common, and depending on the
666 language can vary from restrictive (Reflection in Java or C#) to
667 wide open (CLOS is a perfect example).
669 =head2 Yet Another Class Builder!! Why?
671 This is B<not> a class builder so much as it is a I<class builder
672 B<builder>>. My intent is that an end user does not use this module
673 directly, but instead this module is used by module authors to
674 build extensions and features onto the Perl 5 object system.
676 =head2 Who is this module for?
678 This module is specifically for anyone who has ever created or
679 wanted to create a module for the Class:: namespace. The tools which
680 this module will provide will hopefully make it easier to do more
681 complex things with Perl 5 classes by removing such barriers as
682 the need to hack the symbol tables, or understand the fine details
685 =head2 What changes do I have to make to use this module?
687 This module was designed to be as unintrusive as possible. Many of
688 its features are accessible without B<any> change to your existsing
689 code at all. It is meant to be a compliment to your existing code and
690 not an intrusion on your code base. Unlike many other B<Class::>
691 modules, this module B<does not> require you subclass it, or even that
692 you C<use> it in within your module's package.
694 The only features which requires additions to your code are the
695 attribute handling and instance construction features, and these are
696 both completely optional features. The only reason for this is because
697 Perl 5's object system does not actually have these features built
698 in. More information about this feature can be found below.
700 =head2 A Note about Performance?
702 It is a common misconception that explict MOPs are performance drains.
703 But this is not a universal truth at all, it is an side-effect of
704 specific implementations. For instance, using Java reflection is much
705 slower because the JVM cannot take advantage of any compiler
706 optimizations, and the JVM has to deal with much more runtime type
707 information as well. Reflection in C# is marginally better as it was
708 designed into the language and runtime (the CLR). In contrast, CLOS
709 (the Common Lisp Object System) was built to support an explicit MOP,
710 and so performance is tuned for it.
712 This library in particular does it's absolute best to avoid putting
713 B<any> drain at all upon your code's performance. In fact, by itself
714 it does nothing to affect your existing code. So you only pay for
715 what you actually use.
717 =head2 About Metaclass compatibility
719 This module makes sure that all metaclasses created are both upwards
720 and downwards compatible. The topic of metaclass compatibility is
721 highly esoteric and is something only encountered when doing deep and
722 involved metaclass hacking. There are two basic kinds of metaclass
723 incompatibility; upwards and downwards.
725 Upwards metaclass compatibility means that the metaclass of a
726 given class is either the same as (or a subclass of) all of the
729 Downward metaclass compatibility means that the metaclasses of a
730 given class's anscestors are all either the same as (or a subclass
733 Here is a diagram showing a set of two classes (C<A> and C<B>) and
734 two metaclasses (C<Meta::A> and C<Meta::B>) which have correct
735 metaclass compatibility both upwards and downwards.
737 +---------+ +---------+
738 | Meta::A |<----| Meta::B | <....... (instance of )
739 +---------+ +---------+ <------- (inherits from)
742 +---------+ +---------+
744 +---------+ +---------+
746 As I said this is a highly esoteric topic and one you will only run
747 into if you do a lot of subclassing of B<Class::MOP::Class>. If you
748 are interested in why this is an issue see the paper
749 I<Uniform and safe metaclass composition> linked to in the
750 L<SEE ALSO> section of this document.
752 =head2 Using custom metaclasses
754 Always use the metaclass pragma when using a custom metaclass, this
755 will ensure the proper initialization order and not accidentely
756 create an incorrect type of metaclass for you. This is a very rare
757 problem, and one which can only occur if you are doing deep metaclass
758 programming. So in other words, don't worry about it.
762 The protocol is divided into 4 main sub-protocols:
766 =item The Class protocol
768 This provides a means of manipulating and introspecting a Perl 5
769 class. It handles all of symbol table hacking for you, and provides
770 a rich set of methods that go beyond simple package introspection.
772 See L<Class::MOP::Class> for more details.
774 =item The Attribute protocol
776 This provides a consistent represenation for an attribute of a
777 Perl 5 class. Since there are so many ways to create and handle
778 attributes in Perl 5 OO, this attempts to provide as much of a
779 unified approach as possible, while giving the freedom and
780 flexibility to subclass for specialization.
782 See L<Class::MOP::Attribute> for more details.
784 =item The Method protocol
786 This provides a means of manipulating and introspecting methods in
787 the Perl 5 object system. As with attributes, there are many ways to
788 approach this topic, so we try to keep it pretty basic, while still
789 making it possible to extend the system in many ways.
791 See L<Class::MOP::Method> for more details.
793 =item The Instance protocol
795 This provides a layer of abstraction for creating object instances.
796 Since the other layers use this protocol, it is relatively easy to
797 change the type of your instances from the default HASH ref to other
798 types of references. Several examples are provided in the F<examples/>
799 directory included in this distribution.
801 See L<Class::MOP::Instance> for more details.
811 =item I<IS_RUNNING_ON_5_10>
813 We set this constant depending on what version perl we are on, this
814 allows us to take advantage of new 5.10 features and stay backwards
819 Whether or not C<mro> provides C<get_isarev>, a much faster way to get all the
820 subclasses of a certain class.
824 =head2 Utility functions
828 =item B<load_class ($class_name)>
830 This will load a given C<$class_name> and if it does not have an
831 already initialized metaclass, then it will intialize one for it.
832 This function can be used in place of tricks like
833 C<eval "use $module"> or using C<require>.
835 =item B<is_class_loaded ($class_name)>
837 This will return a boolean depending on if the C<$class_name> has
840 NOTE: This does a basic check of the symbol table to try and
841 determine as best it can if the C<$class_name> is loaded, it
842 is probably correct about 99% of the time.
844 =item B<check_package_cache_flag ($pkg)>
846 This will return an integer that is managed by C<Class::MOP::Class>
847 to determine if a module's symbol table has been altered.
849 In Perl 5.10 or greater, this flag is package specific. However in
850 versions prior to 5.10, this will use the C<PL_sub_generation> variable
851 which is not package specific.
853 =item B<get_code_info ($code)>
855 This function returns two values, the name of the package the C<$code>
856 is from and the name of the C<$code> itself. This is used by several
857 elements of the MOP to detemine where a given C<$code> reference is from.
859 =item B<subname ($name, $code)>
861 B<NOTE: DO NOT USE THIS FUNCTION, IT IS FOR INTERNAL USE ONLY!>
863 If possible, we will load the L<Sub::Name> module and this will function
864 as C<Sub::Name::subname> does, otherwise it will just return the C<$code>
867 =item B<in_global_destruction>
869 If L<Devel::GlobalDestruction> is available, this returns true under global
872 Otherwise it's a constant returning false.
876 =head2 Metaclass cache functions
878 Class::MOP holds a cache of metaclasses, the following are functions
879 (B<not methods>) which can be used to access that cache. It is not
880 recommended that you mess with this, bad things could happen. But if
881 you are brave and willing to risk it, go for it.
885 =item B<get_all_metaclasses>
887 This will return an hash of all the metaclass instances that have
888 been cached by B<Class::MOP::Class> keyed by the package name.
890 =item B<get_all_metaclass_instances>
892 This will return an array of all the metaclass instances that have
893 been cached by B<Class::MOP::Class>.
895 =item B<get_all_metaclass_names>
897 This will return an array of all the metaclass names that have
898 been cached by B<Class::MOP::Class>.
900 =item B<get_metaclass_by_name ($name)>
902 This will return a cached B<Class::MOP::Class> instance of nothing
903 if no metaclass exist by that C<$name>.
905 =item B<store_metaclass_by_name ($name, $meta)>
907 This will store a metaclass in the cache at the supplied C<$key>.
909 =item B<weaken_metaclass ($name)>
911 In rare cases it is desireable to store a weakened reference in
912 the metaclass cache. This function will weaken the reference to
913 the metaclass stored in C<$name>.
915 =item B<does_metaclass_exist ($name)>
917 This will return true of there exists a metaclass stored in the
918 C<$name> key and return false otherwise.
920 =item B<remove_metaclass_by_name ($name)>
922 This will remove a the metaclass stored in the C<$name> key.
930 There are very few books out on Meta Object Protocols and Metaclasses
931 because it is such an esoteric topic. The following books are really
932 the only ones I have found. If you know of any more, B<I<please>>
933 email me and let me know, I would love to hear about them.
937 =item "The Art of the Meta Object Protocol"
939 =item "Advances in Object-Oriented Metalevel Architecture and Reflection"
941 =item "Putting MetaClasses to Work"
943 =item "Smalltalk: The Language"
951 =item Uniform and safe metaclass composition
953 An excellent paper by the people who brought us the original Traits paper.
954 This paper is on how Traits can be used to do safe metaclass composition,
955 and offers an excellent introduction section which delves into the topic of
956 metaclass compatibility.
958 L<http://www.iam.unibe.ch/~scg/Archive/Papers/Duca05ySafeMetaclassTrait.pdf>
960 =item Safe Metaclass Programming
962 This paper seems to precede the above paper, and propose a mix-in based
963 approach as opposed to the Traits based approach. Both papers have similar
964 information on the metaclass compatibility problem space.
966 L<http://citeseer.ist.psu.edu/37617.html>
974 =item The Perl 6 MetaModel work in the Pugs project
978 =item L<http://svn.openfoundry.org/pugs/perl5/Perl6-MetaModel>
980 =item L<http://svn.openfoundry.org/pugs/perl5/Perl6-ObjectSpace>
990 =item CPAN Module Review of Class::MOP
992 L<http://www.oreillynet.com/onlamp/blog/2006/06/cpan_module_review_classmop.html>
996 =head1 SIMILAR MODULES
998 As I have said above, this module is a class-builder-builder, so it is
999 not the same thing as modules like L<Class::Accessor> and
1000 L<Class::MethodMaker>. That being said there are very few modules on CPAN
1001 with similar goals to this module. The one I have found which is most
1002 like this module is L<Class::Meta>, although it's philosophy and the MOP it
1003 creates are very different from this modules.
1007 All complex software has bugs lurking in it, and this module is no
1008 exception. If you find a bug please either email me, or add the bug
1011 =head1 ACKNOWLEDGEMENTS
1017 Thanks to Rob for actually getting the development of this module kick-started.
1023 Stevan Little E<lt>stevan@iinteractive.comE<gt>
1025 B<with contributions from:>
1027 Brandon (blblack) Black
1029 Guillermo (groditi) Roditi
1033 Rob (robkinyon) Kinyon
1035 Yuval (nothingmuch) Kogman
1037 Scott (konobi) McWhirter
1039 =head1 COPYRIGHT AND LICENSE
1041 Copyright 2006-2008 by Infinity Interactive, Inc.
1043 L<http://www.iinteractive.com>
1045 This library is free software; you can redistribute it and/or modify
1046 it under the same terms as Perl itself.