Thanks for reminding us of the Alternatives™ again marto! As I said there are TIMTOWTDI ways to embed perl in html. Why discourage people from having fun with CPAN modules? These things work well enough for our purposes and are fun and productive. Please let us have fun marty!

Lots of stuff written with a module like this stays local anyway. I have tons of useful utilities written with the many methods of cpan in a cgi folder to summon from a browser bookmark list. Significant new os functionality can be cooked up in minutes with a sweet html interface with something like Markup::Perl. Quite a bit can be achieved by dropping the synopsis from some cool module into the <perl> block of the template provided in the pod of the program this node is supposed to be about. Once one likes that kind of home brew ease of use one may want a textarea to paste code samples into; then one might want a pod reader that automatically inserts any listed code into a textarea you can edit and click to try functions of installed modules from inside the documentation. Anyway you'll see more in my next Markup::Perl demo!

If it's a concern keep <perl> blocks large so refactoring doesn't waste code. 👍

---

---

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