> I don't think that's actually happening.
> On a case-sensitive system (which yours is ?) "use B;" will not load b.pm because of the case mismatch.

You are right that 5.26.2 is not ignoring b.pm on my old system, but believe it or not it IS using b.pm, and since the version matched it worked. On my new box 5.38.2 was also trying to use b.pm so I renamed it and the problem evaporated. I'm not using apache on the new box yet, even though macs come with 2.4.56 included, but morbo is not bothered by b.pm for some reason.

I don't know why but on macOS you can type perldoc data::dumper and it will work, but on Linux you must spell it Data::Dumper. You can also use lowercase module names when using them in one liners for OO modules, but to call functions you must use the proper case:

perl -Mdata::dumper -we'$d=Data::Dumper->new(\@ARGV);print$d->Dump' fo
+o bar
[download]

$VAR1 = 'foo';
$VAR2 = 'bar';

perl -Mdata::dumper -we'print Dumper(\@ARGV)' foo bar
[download]

I don't know why but on macOS you can type perldoc data::dumper and it will work, but on Linux you must spell it Data::Dumper

Or simply use the -i flag as intended:

$ perl -E 'say $^O'
linux
$ perldoc -i data::dumper | head
NAME
    Data::Dumper - stringified perl data structures, suitable for both
    printing and "eval"

SYNOPSIS
        use Data::Dumper;

        # simple procedural interface
        print Dumper($foo, $bar);

$
[download]

---

🦛

>> I don't know why but on macOS you can type perldoc data::dumper and it will work, but on Linux you must spell it Data::Dumper

> Or simply use the -i flag as intended

You can do that but the point of my demonstration is that perl seems kinda buggy on a case insensitive file system because there are no warnings nor failures due to mis-capitalized module names.