For a blessfull change, try to use the CODE tag.

Second, read the docs, eg CGI.

Than, your code can be shuffled into:

for my $field ($cgi->param){ $cgi->param($field) =~ s/search/replace/g; }

Try subsequently to rethink your regexes...

Jeroen
"We are not alone"(FZ)

Update /me humbly crawls in the dust, ashamed of the mere suggestion, let alone the naked fact, of the use of $cgi->param as an l-value. I just was not thinking, that's the only thing I can come up with. That's not even an excuse. As a self-proclaimed punishment:

open LETEVERYBODYKNOW, ">/var/www/index.html"; print LETEVERYBODYKNOW "Thou shall not use CGI's param as an l-val +ue\n" for 1..117682;
I believe merlyn and tilly have some runable code, actually.

In reply to Re: form parsing by jeroenes
in thread form parsing by Rotomola

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.