I agree with Perrin in that you should just ask your provider to provide it.

However, another problem then arrises. How can you do this:

BEGIN{
 push (@INC,
"/home/httpd/vhosts/newrisedesigns.com/cgi-bin",
"/home/httpd/vhosts/newrisedesigns.com/cgi-bin/XML",
/home/httpd/vhosts/newrisedesigns.com/cgi-bin/XML/Parser");
}
[download]

in a more elegant way? Well, fortunately there's this option:

use lib '/home/httpd/vhosts/newrisedesigns.com/cgi-bin/XML';
[download]

Insert as many use lib '/path/to/lib/';s as you need to get your program running. Just remember that you need to use the modules in those libraries AFTER you've used those libraries. eg:

use lib '/home/Perllibs/';
use XML::Parser;
[download]

Oh, and Perl will helpfully use the modules in your lib directories in preference to those in the system directories. This means that if your provider is providing an ancient version of something you need, eg CGI, you can get around that by using your own more up-to-date version. Just be wary of accidently calling your modules the same names as built in Perl modules, but this is always a problem. ;)

Good luck.

jarich

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.