comment on

The saint suits his solution to the situation, but uses strict.pm, and with just a small number of arguments prefers individual variables so he gets his beloved typo check. With many, well he tries to avoid that. :-)

The saint also does not like data structures that automatically convert between being regular strings and anonymous arrays. Code like that just forces you to later check for the data type and code stuff twice.

In reply to Re (tilly) 1: Best way to parse CGI params by tilly
in thread Best way to parse CGI params by hakkr

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks