S11 doesn't say how 'require' distinguishes module names and file names about old-design-docs HOT 4 CLOSED

That sounds pretty dangerous -- a 'touch YourModule` in the current working directory could make a working program stop work. And execute code not in @*INC, even though that's not what the programmer meant.

from old-design-docs.

Seems that I accidentally edited my comment. The idea was to check for existence of the file and decide basing on that. I agree that it's probably unsafe though.

from old-design-docs.

I vote for require-file since if I do require Something and mean a file, and later there is a module called Something I get problems...

from old-design-docs.

Maybe have a flag for require, like :file or :path? Or, how jnthn++ suggests, just make decision basing on the type, so one can do require 'foo'.IO or so

from old-design-docs.