use strict;
use warnings;
use HTML::TokeParser::Simple;

my $p = HTML::TokeParser::Simple->new("foo.html");

sub new_form_tag {
    my ($attr) = @_;

    $attr->{value} = "foo"
        if $attr->{name} eq "bar";

    return join " ", "<input", map(qq($_="$attr->{$_}"), keys %$attr),
+ ">";
}

while(my $token = $p->get_token) {
    print $token->is_start_tag('input')
        ? new_input_tag($token->return_attr)
        : $token->as_is;
}

[download]
The $attr->{value} = "foo" if $attr->{name} eq "bar" part can be as complex as desired, obviously.

Makeshifts last the longest.

In reply to Re: Pattern Matching and replacement (tokeparser to the rescue) by Aristotle
in thread Pattern Matching and replacement by Feral_Shade

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.