<rant>
It's better not to try to parse html (and xml) by using regular expressions. I know it's tempting to do so and it also often enough just works for quick and dirty scripts. But if the program has to scale you will soon find it in a big mess.
</rant>

So it's better to use an appropriate module like HTML::Parser or HTML::TokeParser.
use strict; use LWP::Simple; my $url = "http://amazon.com/o/tg/cm/browse-communities/-/" . $circleID . "/t/"; #Request the URL my $content = get($url); die "Could not retrieve $url" unless $content; use HTML::TokeParser; use Data::Dumper; $p = HTML::TokeParser->new(\$content) || die "Can't open: $!"; while (my $token = $p->get_tag( 'title' )) { print Dumper ($token); #... }


holli, /regexed monk/

In reply to Re: Newb wrestles with join by holli
in thread Newb wrestles with join by Dizzley

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.