Sure Adam, you can always use any Perl Module you like. Even if your ISP wont install the module for you. Here is what you do.

1. Download the module.
2. Create A new directory on your server (I would suggest somthing like: perlmods/The Module Name Here/).
3. Decompress the module you downloaded (if needed).
4. Upload *ALL* the decompressed files to the directory you created on the server.
5. Make sure the directory & the files you put on the server have Read, Write & Execute permissions, if your server requires to set permissions.
6. Add

use lib '~myname/path/to/perlmods/The Module Name Here';
use javascript;
[download]

use lib simply adds the list of paths that you specify to the front of @INC and thus they get searched first for any modules. While you can't easily maintain the modules with CPAN, you can still grab the source for each, and specify YOUR directory for all install work.

Simply uncompressing module tarballs or .zip files and putting them in a particular place isn't always going to do the job right. There's a standard procedure for installing Perl modules, and there's no problem with installing them into any directory to which you have write permissions.

perl Makefile.PL PREFIX=path/to/my/modules
make
make test #(optional)
make install
[download]

The <coe>PREFIX</code> argument to Makefile.PL is the key here; if you omit it, the installation will point to the system-wide @INC directories, which are usually (because they ought to be) only writeable by the superuser. See your system's perldoc perlmodinstall for more goodies like this.

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

arturo, I must have misunderstood the info in Re: Seeking wisdom again... by Masem. Thank You for correcting me.

heyman, I applogize if I have given you mis-information. I'm still learning. :)