Erman Duyar wrote:

As I mentioned in my report, I am aware of the workarounds. However, I
reported this bug because I believe the current behavior is counterintuitive
and inhibits self-contained modular programs.
It was a design choice, and since it has always (for a *very* long time at
least) been that way, because of backwards compatibility issues, it is not
something that can be changed. It is very much a religious argument, much like
some [older] *nix configurations have '.' as the first element of PATH, and most
[modern] don't include the current directory at all.

It is usually wrong (IMNSHO) to override system-path modules with local modules
with the same name (but possibly very different API's). If you don't want to
install your modules [in a private namespace] and use the normal @INC resolution
rules, you are free to override that behavior by the workarounds mentioned, just
as you are free to change your search PATH in your personal shell script.
Is there a real reason for not
adding the script/module directory to the beginning of the search path?
Security? Consistency? That's not the way Perl was designed?


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Blvd
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 5 of 6 | next ›
Discussion Overview
groupperl5-porters @
postedAug 8, '07 at 4:30a
activeAug 9, '07 at 6:38p



site design / logo © 2019 Grokbase