use strict;
use warnings;
-use Scalar::Util 'blessed';
use Carp 'confess';
-use SUPER ();
+use Scalar::Util ();
use Class::MOP::Class;
use Class::MOP::Attribute;
our $VERSION = '0.07';
-sub import {
- shift;
- return unless @_;
- if ($_[0] eq ':universal') {
- *UNIVERSAL::meta = sub {
- Class::MOP::Class->initialize(blessed($_[0]) || $_[0])
- };
- }
- else {
- my $pkg = caller();
- no strict 'refs';
- *{$pkg . '::' . $_[0]} = sub {
- Class::MOP::Class->initialize(blessed($_[0]) || $_[0])
- };
- }
-}
+## ----------------------------------------------------------------------------
+## Setting up our environment ...
+## ----------------------------------------------------------------------------
+## Class::MOP needs to have a few things in the global perl environment so
+## that it can operate effectively. Those things are done here.
+## ----------------------------------------------------------------------------
+
+# so that mixins can have runtime
+# dispatched SUPER calls
+use SUPER ();
## ----------------------------------------------------------------------------
## Bootstrapping
I<Uniform and safe metaclass composition> linked to in the
L<SEE ALSO> section of this document.
+=head2 Using custom metaclasses
+
+Always use the metaclass pragma when using a custom metaclass, this
+will ensure the proper initialization order and not accidentely
+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.
+
=head1 PROTOCOLS
The protocol is divided into 3 main sub-protocols: