From: Nicholas Clark <nick@ccl4.org>
Date: Sat, 27 Dec 2008 08:39:14 +0000 (+0000)
Subject: Remove the comment that the mro:: functions are actually in the core
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=58d4c5dfb9bcf0d0f30468212e01c1f9c9d48ce3;p=p5sagit%2Fp5-mst-13.2.git

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.
---

diff --git a/ext/mro/mro.pm b/ext/mro/mro.pm
index 5f0ae96..5a193e2 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