That's fine. I just look at it from a Filter author perspective. I had
a bug submitted against mine regarding this. The API was implemented,
I just didn't subclass. If you aren't going to add the checks I would
at least recommend making a documentation change to the POE::Filter
POD that makes a point of subclassing instead of "These methods are
the generic Filter interface, and every filter must implement them.
Specific filters may have additional methods." which tells me, a
Filter author, that subclassing isn't required. Also, Wheels don't do
this checking, and maybe they should. If Filter::Stackable is going to
require POE::Filter subclassed references then it should be consistent
across the board.
On 10/30/06, via RT <bug-POE@rt.cpan.org> wrote:
Show quoted text>
> <URL:
http://rt.cpan.org/Ticket/Display.html?id=22633 >
>
> I think the debugging help isn't worth the extra runtime checks. This
> is going to fail early and with certainty, and it's not hard to figure
> the problem's cause.
>
> Sorry for suggesting that you make this a ticket; I wasn't really
> thinking about it at the time.
>