Appreciate the responses... for the record, I am what I once heard described as a 'perl Puritan' and have '-w' and 'use strict' in every script I write. There's some handy reasons for using import_names, mostly because it makes it much easier to handle param() values in here_docs.
The reason this is important to me is that I have a function generating a form... and so as to not get a ton of 'uninit'd value' warnings, at the top of this function I have a %values hash that does this:
%values = (
\t input_value => $ref->{ input_value } || $PARAM::input_value || ''
\t );
... and then the input element uses $values{ input_value } where appropriate. This lets you pass in a reference to a DBI statement fetchrow_hashref and covers your bases should there be some mixup. My question arose when I do any type of form verification and return the user to the form... under certain circumstances, I don't want %values to hold the param() info.
In any case, I appreciate the input... take care, folks.
markguy
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.