Hello everyone,
How about creating Text::Filter::LowerCase and
> Text::Filter::Unpunctuate as derived classes of Text::Filter?
I had peeked at Text::Filter before, and had deemed it great as a transport mechanism (handling various in- and outputs, which my module deliberately would *not* cover), but I had left with the impression that this was strictly line-based, which is not enough for some of the filters I'm planning, and couldn't handle filter parameters.
However, I've had another look, and discovered the peek-and-pushback mechanisms. So I'll subclass Text::Filter.
I'm now going with Text::Filter::Lossy, since I want to keep (most of the) filters in one place, and also to enable easy programmatic sub-filter selection, for example from command line arguments.
Thanks for the pointers, everyone! Ben Deutsch
