I think it was just dragonchild mis-remembering the name of the design pattern - what you're after isn't a facade.

Filters/Pipelines are such a common idiom I have to believe that somebody has documented it as a design pattern somewhere... possibly in a PLoP proceeding. However, I don't have an academic library available to check :-)

I think there's a little confusion because the terms "filtering" and "pipelining" are more often used for applying a series of transformations to something - rather than a series of predicates that exclude objects. From your post I think you're after the latter.

A more concrete example of what you, in particular, are attempting would help. As somebody else already pointed out grep does what you want in simple cases.

If you need to build objects that can apply specific filters, something like this:

#! /usr/bin/perl

package Sieve;
use strict;
use warnings;

sub new { bless [], shift };

sub add_predicate {
    my $self = shift;
    push @$self, shift;
}

sub ok {
    my ($self, $item) = @_;
    $_->($item) || return(0) foreach @$self;
    return(1);
};

sub sieve {
    my $self = shift;
    grep {$self->ok($_)} @_;
};
[download]

allows you to do:

my $o = Sieve->new;
$o->add_predicate( sub { $_[0] > 5 } );
$o->add_predicate( sub { $_[0] % 2 } );

my @original = (1..15);
my @sieved = $o->sieve( @original );
print "original: @original\n";
print "odd numbers > 5 are: @sieved\n";

__END__
producing

original: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
odd numbers > 5 are: 7 9 11 13 15
[download]

If you need more - you'll have to give up a bit more detail ;-)