PLP doesn't require mod_perl, but it is recommended if you'll be running any large scripts. Mod_perl sort of 'embeds' a resident perl interpreter in Apache, which in turn caches your perl-scripts in memory. That way perl doesn't have to be loaded on each CGI request, and perl doesn't have to recompile your script on every request.

On the PLP page are instructions for the system administrators on how to use PLP both with and without CGI. After they've done that, you'll be able to 'use' PLP without useing it... It's a module you'll never invoke directly. It is invoked by the webserver and allows you to create .plp scripts instead op .pl scripts.

If you want to see examples of .plp pages, just visit the homepage for PLP (http://plp.juerd.nl/) and on any page click 'Page Source' in the left navigation bar. The main advantage to PLP is that it debugs easier than plain CGI, and it can be used to easily build html-templates, so you don't have to hardcode your html in your scripts.

The benefits of stuff like this will become obvious once you've gotten started using it... :)

Regards, Gilimanjaro...

---

---

• 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.