summaryrefslogtreecommitdiff
path: root/ext/mro
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2008-12-27 08:39:14 +0000
committerNicholas Clark <nick@ccl4.org>2008-12-27 21:12:13 +0000
commit58d4c5dfb9bcf0d0f30468212e01c1f9c9d48ce3 (patch)
tree77859a88ee2b30ab0e06050f316f34222b97cee3 /ext/mro
parentb2685f0c86badfc357584d8dbfb2bf17057ea226 (diff)
downloadperl-58d4c5dfb9bcf0d0f30468212e01c1f9c9d48ce3.tar.gz
Remove the comment that the mro:: functions are actually in the core
interpreter, hence you don't actually need to use mro; This should have remained an implementation detail, as it limits the scope to move things around within a stable branch. So for now, remove the expectation.
Diffstat (limited to 'ext/mro')
-rw-r--r--ext/mro/mro.pm3
1 files changed, 1 insertions, 2 deletions
diff --git a/ext/mro/mro.pm b/ext/mro/mro.pm
index 5f0ae9683e..5a193e2c8c 100644
--- a/ext/mro/mro.pm
+++ b/ext/mro/mro.pm
@@ -68,8 +68,7 @@ implementation for older Perls.
It's possible to change the MRO of a given class either by using C<use
mro> as shown in the synopsis, or by using the L</mro::set_mro> function
-below. The functions in the mro namespace do not require loading the
-C<mro> module, as they are actually provided by the core perl interpreter.
+below.
The special methods C<next::method>, C<next::can>, and
C<maybe::next::method> are not available until this C<mro> module