Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

poe::filter::grep(3pm) [debian man page]

POE::Filter::Grep(3pm)					User Contributed Perl Documentation				    POE::Filter::Grep(3pm)

NAME
POE::Filter::Grep - select or remove items based on simple rules SYNOPSIS
#!perl use POE qw( Wheel::FollowTail Filter::Line Filter::Grep Filter::Stackable ); POE::Session->create( inline_states => { _start => sub { my $parse_input_as_lines = POE::Filter::Line->new(); my $select_sudo_log_lines = POE::Filter::Grep->new( Put => sub { 1 }, Get => sub { my $input = shift; return $input =~ /sudo[d+]/i; }, ); my $filter_stack = POE::Filter::Stackable->new( Filters => [ $parse_input_as_lines, # first on get, last on put $select_sudo_log_lines, # first on put, last on get ] ); $_[HEAP]{tailor} = POE::Wheel::FollowTail->new( Filename => "/var/log/system.log", InputEvent => "got_log_line", Filter => $filter_stack, ); }, got_log_line => sub { print "Log: $_[ARG0] "; } } ); POE::Kernel->run(); exit; DESCRIPTION
POE::Filter::Grep selects or removes items based on simple tests. It may be used to filter input, output, or both. This filter is named and modeled after Perl's built-in grep() function. POE::Filter::Grep is designed to be combined with other filters through POE::Filter::Stackable. In the "SYNOPSIS" example, a filter stack is created to parse logs as lines and remove all entries that don't pertain to a sudo process. (Or if your glass is half full, the stack only selects entries that DO mention sudo.) PUBLIC FILTER METHODS
In addition to the usual POE::Filter methods, POE::Filter::Grep also supports the following. new new() constructs a new POE::Filter::Grep object. It must either be called with a single Code parameter, or both a Put and a Get parameter. The values for Code, Put, and Get are code references that, when invoked, return true to select an item or false to reject it. A Code function will be used for both input and output, while Get and Put functions allow input and output to be filtered in different ways. The item in question will be passed as the function's sole parameter. sub reject_bidoofs { my $pokemon = shift; return 1 if $pokemon ne "bidoof"; return; } my $gotta_catch_nearly_all = POE::Filter::Grep->new( Code => &reject_bidoofs, ); Enforce read-only behavior: my $read_only = POE::Filter::Grep->new( Get => sub { 1 }, Put => sub { 0 }, ); modify modify() changes a POE::Filter::Grep object's behavior at run-time. It accepts the same parameters as new(), and it replaces the existing tests with new ones. # Don't give away our Dialgas. $gotta_catch_nearly_all->modify( Get => sub { 1 }, Put => sub { return shift() ne "dialga" }, ); SEE ALSO
POE::Filter for more information about filters in general. POE::Filter::Stackable for more details on stacking filters. BUGS
None known. AUTHORS &; COPYRIGHTS The Grep filter was contributed by Dieter Pearcey. Documentation is provided by Rocco Caputo. Please see the POE manpage for more information about authors and contributors. perl v5.14.2 2012-05-15 POE::Filter::Grep(3pm)

Check Out this Related Man Page

POE::Filter::IRC::Compat(3pm)				User Contributed Perl Documentation			     POE::Filter::IRC::Compat(3pm)

NAME
POE::Filter::IRC::Compat - A filter which converts POE::Filter::IRCD output into POE::Component::IRC events SYNOPSIS
my $filter = POE::Filter::IRC::Compat->new(); my @events = @{ $filter->get( [ @lines ] ) }; my @msgs = @{ $filter->put( [ @messages ] ) }; DESCRIPTION
POE::Filter::IRC::Compat is a POE::Filter that converts POE::Filter::IRCD output into the POE::Component::IRC compatible event references. Basically a hack, so I could replace POE::Filter::IRC with something that was more generic. Among other things, it converts normal text into thoroughly CTCP-quoted messages, and transmogrifies CTCP-quoted messages into their normal, sane components. Rather what you'd expect a filter to do. A note: the CTCP protocol sucks bollocks. If I ever meet the fellow who came up with it, I'll shave their head and tattoo obscenities on it. Just read the "specification" (docs/ctcpspec.html in this distribution) and you'll hopefully see what I mean. Quote this, quote that, quote this again, all in different and weird ways... and who the hell needs to send mixed CTCP and text messages? WTF? It looks like it's practically complexity for complexity's sake -- and don't even get me started on the design of the DCC protocol! Anyhow, enough ranting. Onto the rest of the docs... METHODS
"new" Returns a POE::Filter::IRC::Compat object. Takes no arguments. "clone" Makes a copy of the filter, and clears the copy's buffer. "get" Takes an arrayref of POE::Filter::IRCD hashrefs and produces an arrayref of POE::Component::IRC compatible event hashrefs. Yay. "get_one_start", "get_one" These perform a similar function as "get" but enable the filter to work with POE::Filter::Stackable. "put" Takes an array reference of CTCP messages to be properly quoted. This doesn't support CTCPs embedded in normal messages, which is a brain- dead hack in the protocol, so do it yourself if you really need it. Returns an array reference of the quoted lines for sending. "debug" Takes an optinal true/false value which enables/disables debugging accordingly. Returns the debug status. "chantypes" Takes an arrayref of possible channel prefix indicators. "identifymsg" Takes a boolean to turn on/off the support for CAPAB IDENTIFY-MSG. AUTHOR
Chris 'BinGOs' Williams SEE ALSO
POE::Filter::IRCD POE::Filter POE::Filter::Stackable perl v5.14.2 2011-12-07 POE::Filter::IRC::Compat(3pm)
Man Page