New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use Module; fails silently with wrong cased module name on Windows #14926
Comments
From beasley@web.deCreated by beasley@web.deSome code to illustrate the Problem: C:\data\bla>echo package Module; sub import { print "Import called.\n"; }; 1;
C:\data\bla>perl -E "use Module; print 'Called.';" C:\data\bla>perl -E "use MODULE; print 'Called.';" C:\data\bla>perl -E "use MOE; print 'Called.';" C:\data\bla>perl -v (Strawberry Perl installed by berrybrew) Perl Info
|
From @karenetheridgeOn Thu Sep 24 10:35:32 2015, beasley@web.de wrote:
Isn't this expected behaviour for case-insensitive filesystems? |
The RT System itself - Status changed from 'new' to 'open' |
From zefram@fysh.orgPatrick Zimmermann wrote:
This is a known problem, and the natural result of the combination of Finally, the ->import method is called on the package corresponding to The result is less than awesome. But no part of the structure that Incidentally, I've seen the same result from a module file that misspelled My main opinion on this is that the filesystem lookup method should -zefram |
Migrated from rt.perl.org#126167 (status was 'open')
Searchable as RT126167$
The text was updated successfully, but these errors were encountered: