use strict;
use warnings;
-our $VERSION = '0.24';
+our $VERSION = '0.29';
our $C3_IN_CORE;
our $C3_XS;
my %methods;
# NOTE:
# we do @MRO[1 .. $#MRO] here because it
- # makes no sense to interogate the class
+ # makes no sense to interrogate the class
# which you are calculating for.
foreach my $local (@MRO[1 .. $#MRO]) {
# if overload has tagged this module to
$has_overload_fallback = ${"${local}::()"}
if !defined $has_overload_fallback && defined ${"${local}::()"};
foreach my $method (grep { defined &{"${local}::$_"} } keys %{"${local}::"}) {
- # skip if already overriden in local class
+ # skip if already overridden in local class
next unless !defined *{"${class}::$method"}{CODE};
$methods{$method} = {
orig => "${local}::$method",
=head1 SYNOPSIS
# NOTE - DO NOT USE Class::C3 directly as a user, use MRO::Compat instead!
- package A;
+ package ClassA;
use Class::C3;
sub hello { 'A::hello' }
- package B;
- use base 'A';
+ package ClassB;
+ use base 'ClassA';
use Class::C3;
- package C;
- use base 'A';
+ package ClassC;
+ use base 'ClassA';
use Class::C3;
sub hello { 'C::hello' }
- package D;
- use base ('B', 'C');
+ package ClassD;
+ use base ('ClassB', 'ClassC');
use Class::C3;
# Classic Diamond MI pattern
# (formerly called in INIT)
Class::C3::initialize();
- print join ', ' => Class::C3::calculateMRO('Diamond_D') # prints D, B, C, A
+ print join ', ' => Class::C3::calculateMRO('ClassD'); # prints ClassD, ClassB, ClassC, ClassA
- print D->hello() # prints 'C::hello' instead of the standard p5 'A::hello'
+ print ClassD->hello(); # prints 'C::hello' instead of the standard p5 'A::hello'
- D->can('hello')->(); # can() also works correctly
- UNIVERSAL::can('D', 'hello'); # as does UNIVERSAL::can()
+ ClassD->can('hello')->(); # can() also works correctly
+ UNIVERSAL::can('ClassD', 'hello'); # as does UNIVERSAL::can()
=head1 DESCRIPTION
=head2 What is C3?
C3 is the name of an algorithm which aims to provide a sane method resolution order under multiple
-inheritance. It was first introduced in the langauge Dylan (see links in the L<SEE ALSO> section),
+inheritance. It was first introduced in the language Dylan (see links in the L<SEE ALSO> section),
and then later adopted as the preferred MRO (Method Resolution Order) for the new-style classes in
Python 2.3. Most recently it has been adopted as the 'canonical' MRO for Perl 6 classes, and the
default MRO for Parrot objects as well.
though B<C> is the subclass of B<A>. The C3 MRO algorithm however, produces the following MRO
(D, B, C, A), which does not have this same issue.
-This example is fairly trival, for more complex examples and a deeper explaination, see the links in
+This example is fairly trivial, for more complex examples and a deeper explanation, see the links in
the L<SEE ALSO> section.
=head2 How does this module work?
package MyClass;
use c3;
-The the more clunky:
+This is more clunky:
package MyClass;
use Class::C3;
-But hey, it's your choice, thats why it is optional.
+But hey, it's your choice, that's why it is optional.
=head1 FUNCTIONS
This function used to be called automatically for you in the INIT phase of the perl compiler, but
that lead to warnings if this module was required at runtime. After discussion with my user base
(the L<DBIx::Class> folks), we decided that calling this in INIT was more of an annoyance than a
-convience. I apologize to anyone this causes problems for (although i would very suprised if I had
+convenience. I apologize to anyone this causes problems for (although I would be very surprised if I had
any other users other than the L<DBIx::Class> folks). The simplest solution of course is to define
your own INIT method which calls this function.
=item Use of C<SUPER::>.
-The idea of C<SUPER::> under multiple inheritance is ambiguous, and generally not recomended anyway.
-However, its use in conjuntion with this module is very much not recommended, and in fact very
+The idea of C<SUPER::> under multiple inheritance is ambiguous, and generally not recommended anyway.
+However, its use in conjunction with this module is very much not recommended, and in fact very
discouraged. The recommended approach is to instead use the supplied C<next::method> feature, see
more details on its usage above.
It is the author's opinion that changing C<@ISA> at runtime is pure insanity anyway. However, people
do it, so I must caveat. Any changes to the C<@ISA> will not be reflected in the MRO calculated by this
module, and therefore probably won't even show up. If you do this, you will need to call C<reinitialize>
-in order to recalulate B<all> method dispatch tables. See the C<reinitialize> documentation and an example
+in order to recalculate B<all> method dispatch tables. See the C<reinitialize> documentation and an example
in F<t/20_reinitialize.t> for more information.
=item Adding/deleting methods from class symbol tables.
-This module calculates the MRO for each requested class by interogating the symbol tables of said classes.
+This module calculates the MRO for each requested class by interrogating the symbol tables of said classes.
So any symbol table manipulation which takes place after our INIT phase is run will not be reflected in
the calculated MRO. Just as with changing the C<@ISA>, you will need to call C<reinitialize> for any
changes you make to take effect.
=over 4
-=item L<http://www.webcom.com/haahr/dylan/linearization-oopsla96.html>
+=item L<https://web.archive.org/web/20000817033012id_/http://www.webcom.com/haahr/dylan/linearization-oopsla96.html>
=back
projects / gitmo/Class-C3.git / blobdiff