I have the same problem with a client of mine -- unfortunately, unless you
have your own server, your stuck with their setup.
I've gotten around the problem using the I switch in the shebang line:
#!/usr/bin/perl -I./lib
after than, I can include any module living in my lib directory the same
>
>I seem to have found some resolution to my problem. I am using strict and
>had been using the module that resides in the standard libs as follows:
>
>use NYT::Cnxdb;
>
>my $cnxdb = NYT::Cnxdb->new
>
>when I say my $cnxdb = Cnxdb->new
>instead, it works. I was assuming that strict would want
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
At 02:23 PM 5/21/01 -0400, 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 li
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" directive to add thi
Not being familiar with Sun: Have you tried using the REQUIRE keyword in
your script? (require "write_complete_path_here/Modulename.pm") In Win,
which I'm forced to use: it's analogous to having your module resided on a
shared folder, s, and would be
require "s:/folder1/folder2/Modulen
