& XSLT * Robin Berjon <robin.berjon@[...].fr>  [2005-10-24 22:35]:
>  The normalizing filter could detect that the next step in the
>  pipeline is another instance of itself and replace it with
>  that instance's handler. It shouldn't be unduly hard, it
>  wouldn't break anything, and it would allow both the producer
>  and the handler to be defensive with no overhead.

This works reliably only if everyone uses the same filter. I
would instead prefer to have to explicitly request the fixup
filter with something like `Fixup_Filter =>  1` when Iâ??m
constructing a handler, and the handler would wrap itself and
return the wrapper. That way people whoâ??re coding against a
specific handler can exploit its known convenience features
whereas those whoâ??re coding for generality can do the wrapping
explicitly without any fuss. Plus it avoids putting a bunch of
hairy magic in the handlers and the fixup filter.

I prefer that my software try not to be dumb rather than try to
be smart.

Regards,
-- 
#Aristotle
*AUTOLOAD=*_=sub{s/(.*)::(.*)/print$2,(",$\/"," ")[defined wantarray]/e;$1};
&Just-> another->Perl->hacker;
_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs