jeffa's node made me realize I missed a few things.
First, why do a substitution on the body string,
it is unnecessary, a match is all you need.
To use that javascript example you'd need
to support URL's in the subject. So all in all
I'd imagine you'd want to support a single URL
in the subject (and use the body for annotation?),
or one+ URL in the body (you currently support):
Untested
my $URL = qr/(http:\/\/[^\s]*)/;
#Since we use the expression twice it's nice to have it
#as a variable.
#[TheDamian]'s [cpan://Regexp::Common] would be useful once it
#supplies URL matching
#Until then you might want to expand this, it doesn't
#support port numbers or FTP.
for (my $i=1; $i <= $pop->Count(); $i++) # Loop through messages
{
#Support personal toolbar button for spontaneity linking
foreach( $pop->Head($i) ) {
#If you wanted to get fancy you could use Head in scalar
#context with multi-line regexp and avoid the foreach
if( /^Subject:\s+$RE/i ){;
push @linkList, $1;
print "$1\n";
#fetch body for description here if you want
next;
}
}
my $body = $pop->Body($i);
#Just a match ma'am
while ($body =~ /$RE/)
{
push @linkList, $1;
print "$1\n";
}
$pop->Delete($i);
}
$pop->Close();
--
perl -p -e "s/(?:\w);([st])/'\$1/mg"
-
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.
|