Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Also move the calculation of test count earlier, and remove a prototype which isn't needed to force correct parsing. All the other Data::Dumper tests unconditionally assume Test::More, so it's reasonable for this test to make the same assumption. Given that we now specify a minimal Perl version of 5.8.1, this doesn't introduce an external dependency. It seems that the original intent of the tests were that the pure-perl implementation of Data::Dumper could be used as a test of/tested with miniperl. However, the ability to load it with miniperl was lost/broken in Jan 2005 by commit a76739e: Fix spurious warnings emitted by XSLoader via Data::Dumper p4raw-id: //depot/perl@23851 and no-one has actually noticed this for 15 years. By the time the loader code was fixed so that miniperl *could* load it, the "pure perl" Data::Dumper required several routines from Scalar::Util, which (in turn) won't load with miniperl. ("pure perl" is unfortunately an overloaded concept once one considers bootstrapping the core. For CPAN "pure perl" means is "the distribution and all its dependencies on CPAN can be built without a C compiler", which is useful for constrained environments. But for building the core itself there is always a C compiler. It's dynamic loading of core's own C extensions that isn't possible with miniperl, and what matters during the build/when you're debugging a change that breaks things badly with no obvious cause.) Hence there is no advantage in constraining Data::Dumper to be testable without Test::More, because both have the same dependencies.
- Loading branch information