projects / p5sagit/p5-mst-13.2.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b2685f0)
Remove the comment that the mro:: functions are actually in the core
authorNicholas Clark <nick@ccl4.org>
Sat, 27 Dec 2008 08:39:14 +0000 (08:39 +0000)
committerNicholas Clark <nick@ccl4.org>
Sat, 27 Dec 2008 21:12:13 +0000 (21:12 +0000)
commit58d4c5dfb9bcf0d0f30468212e01c1f9c9d48ce3
tree77859a88ee2b30ab0e06050f316f34222b97cee3tree | snapshot
parentb2685f0c86badfc357584d8dbfb2bf17057ea226commit | diff
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.
ext/mro/mro.pm diff | blob | blame | history
Unnamed repository; edit this file to name it for gitweb.