in reply to Re^3: When is it better to NOT release a new module?
in thread When is it better to NOT release a new module?

Its much less sane to do that when you're releasing things onto CPAN where it will have to deal with anything that's potentially available.
Excuse me? Since when is it a requirement that anything released on CPAN needs "to deal with anything that's potentially available"? Answer: never.

CPAN never has, and never will put any requirements on the code stored there, other than its license should allow distribution. If there were such requirements, we wouldn't have a gazillion Class::* modules, many of which don't play nice with each other.

If you don't want to use source filters - don't. Just don't go on a crusade claiming they are universally evil and people shouldn't put modules on CPAN that use source filters. CPAN is open for everyone - and that includes open for code that uses techniques you don't like.

Perl --((8:>*
  • Comment on Re^4: When is it better to NOT release a new module?

Replies are listed 'Best First'.
Re^5: When is it better to NOT release a new module?
by diotalevi (Canon) on Nov 03, 2005 at 14:24 UTC

    I would tend to wish, vainly, that authors would put good faith efforts into doing things that were generally useful and that don't have mysterious failuremodes, that work equally well on multiple platforms (or at least with that intention), that don't fail just because my other perl code didn't look enough like what the author expected. Its a wish. A vain wish. I know. It is unhelpful to have you point out that it is nothing more than a wish and I also wish you hadn't done that. Actually, I think its more than a wish but a bit of a community expectation that authors should at least try for that. I expect that one way of reaching those goals is to avoid such obviously perilous and known impossible jobs. Impossible in the general sense anyway, I'm quite sure that the author's code works more often than it doesn't mostly because I have faith that the author put at least a little bit of effort into it.

    People who don't even try to make reasonable stuff for CPAN ought to have something anatomically improbable done to them. I wish them ill and hope their efforts fail everywhere they go.

    The only non-parse related method I know to rewrite perl code is to treat perl like lisp and rewrite it at the optree level. At least then there are no ambiguities about how something is parsed - its all been handled by the perl parser. But then, perl is an exceptionally ugly lisp when viewed from that direction.

Re^5: When is it better to NOT release a new module?
by diotalevi (Canon) on Nov 03, 2005 at 14:41 UTC
    That first response was all pretty irrational as I was just flummoxed and upset that you'd actually make that point to me. Yes, source filters can work. Apparently there's one that POE uses internally. I just resent the proliferation of known buggy techniques and would prefer to give no quarter to them. This happens to be something that's well known as impossible to get right 100% of the time. Maybe its actually pretty high now that stuff like Filter::Util exists. I dunno. I'll likely never reach for it as I don't know of any circumstance where it would be the right enough tool to allow introducing its quantum weirdness into my code.