NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Text::Pipe? (Score:1)
And I wouldn't put the factory in a
Several pipe segments, piped together, could themselves be pipe segments.
Text::Pipe::* objects could have '|' overloaded so you can combine them in a TT-like syntax.
Then again, maybe you don't want to limit yourself to piping text; how about arbitrary data structures? E.g., one pipe segment could take an array and reduce(). But maybe that's going too far. (I've had such an idea many years ago but didn't follow up on it.) Piping text is fine.
Your example regex that deals with erroneous spaces would itself by a pipe segment, something like Text::Pipe::Trim.
Reply to This
Re: (Score:2)
filterinterface, you don't need to.Creating a stacked pipe is easy by creating a new Pipe stacker object, like:
Re: (Score:1)
my $stacked_pipe = Text::Pipe::Stackable->new($pipe1, $pipe2, $pipe3);
Yes, that's a better design pattern. In that case, Text::Pipe::Stackable->new() should be able to take both individual segments as well as Text::Pipe::Stackable objects as well (for a kind of recursive construction).
That is, stacked pipes should - to the user - be indistinguishable from individual pipe segments. It's just some black hole that has an i
Re: (Score:2)