A short thing on the synopsis - drop the alternatives. A good synopsis should have as much ready-to-copy code as possible.
I would rewrite the synopsis as follows:
use URI::SearchTerms; my $search_url = "http://www.google.com/search?q=foo+bar+baz"; my @terms = URI::SearchTerms->terms($search_url); print join ":", @terms, "\n";
All the finer things, like calling alternatives should go in the detailed discussion of every function (that is, into the discussion of terms()).
Whether you use the class-style call or the fully qualified style call is a matter of taste, and I'm not exactly sure which one I prefer - I guess both are relatively valid, as there is not much use to pass more than one search url to the function.
perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ; # The $d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider ($c = $d->accept())->get_request(); $c->send_response( new #in the HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' # web
In reply to Re: RFC: URI::SearchTerms
by Corion
in thread RFC: URI::SearchTerms
by The Mad Hatter
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |