I do, naturally, have the very same difficulty with understanding abstractions in documentation as I have with them in actual code. I scanned the documentation for parts that I thought I could understand, and did not look closely at the rest. Obviously, I had mistaken the module for being a compatible replacement to CGI. It isn't, and therefore is not suited to my needs.
It reminds me a little of an AJAX module I once incorporated into my scripts. It worked for awhile, until I discovered it was occasionally doing something unpredictable, and altering my data during transfers--resulting in errors in the database. That's when I learned to program the AJAX for myself, and kicked the module to the proverbial curb, never to be needed again (and those errors have not recurred). I often find the need to do things myself, as what others have done is not compatible. I doubt I am alone in this.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.