diff options
author | Piotr Fusik <pfusik@op.pl> | 2005-07-31 14:50:04 +0200 |
---|---|---|
committer | H.Merijn Brand <h.m.brand@xs4all.nl> | 2005-08-02 10:39:51 +0000 |
commit | 3c4b39bee8832007b7e91bfce8701d34cacab411 (patch) | |
tree | 190f72b72255db85e5c78f68a0d0047692aab3a9 /lib/NEXT.pm | |
parent | db30010093a0bacd16d1fa3fd1bd5397da6479d3 (diff) | |
download | perl-3c4b39bee8832007b7e91bfce8701d34cacab411.tar.gz |
Typos in *.p[lm]
From: "Piotr Fusik" <pfusik@op.pl>
Message-ID: <001401c595bd$dccb5d80$0bd34dd5@piec>
p4raw-id: //depot/perl@25261
Diffstat (limited to 'lib/NEXT.pm')
-rw-r--r-- | lib/NEXT.pm | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/NEXT.pm b/lib/NEXT.pm index 1c6a316fff..51dec91964 100644 --- a/lib/NEXT.pm +++ b/lib/NEXT.pm @@ -233,7 +233,7 @@ do better. By default, if a redispatch attempt fails to find another method elsewhere in the objects class hierarchy, it quietly gives up and does -nothing (but see L<"Enforcing redispatch">). This gracious acquiesence +nothing (but see L<"Enforcing redispatch">). This gracious acquiescence is also unlike the (generally annoying) behaviour of C<SUPER>, which throws an exception if it cannot redispatch. @@ -420,7 +420,7 @@ order. Instead, they are called "breadth-first-dependency-wise". That means that the inheritance tree of the object is traversed breadth-first and the resulting order of classes is used as the sequence in which methods are called. However, that sequence is modified by imposing a rule that the -appropritae method of a derived class must be called before the same method of +appropriate method of a derived class must be called before the same method of any ancestral class. That's why, in the above example, C<X::foo> is called before C<D::foo>, even though C<D> comes before C<X> in C<@B::ISA>. |