pting to develop my first module. Because of
>permissions/security, etc.. I cannot store the module in the standard
>perl lib directories. So it is currently living in a subdir called lib in
>my home directory. I use a "use lib" directive to add this directory to
>@INC
ib directories. So it is currently living in a subdir called lib in my
>>: home directory. I use a "use lib" directive to add this directory to
>>: @INC. this works , but when I try then to use another module that does
>>: reside in the standard lib directories, I get a
I wrote:
: If you did, then did you use the same perl executable to install the
: module that you're using to run it? i.e., does 'which perl' eq the
: shebang line of your script? If you have two perls on your system
: (seems a lot of people do), then it may be that the other module isn't
: inst
I use a "use lib" directive to add this directory to
>@INC. this works , but when I try then to use another module that does
>reside in the standard lib directories, I get a "Can't locate object
>method "new" in module "X" at path-specified-
Peter Cline wrote:
: Hello, I am attempting to develop my first module. Because of
: permissions/security, etc.. I cannot store the module in the standard perl
: lib directories. So it is currently living in a subdir called lib in my
: home directory. I use a "use lib" direct
gt;perl lib directories. So it is currently living in a subdir called lib in
>my home directory. I use a "use lib" directive to add this directory to
>@INC. this works , but when I try then to use another module that does
>reside in the standard lib directories, I get a &quo
Hello, I am attempting to develop my first module. Because of
permissions/security, etc.. I cannot store the module in the standard perl
lib directories. So it is currently living in a subdir called lib in my
home directory. I use a "use lib" directive to add this directory to
@
