Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Re^3: How to complain about changes to a module? (And what good would it do?)

by Corion (Pope)
on Aug 29, 2008 at 05:58 UTC ( #707664=note: print w/replies, xml ) Need Help??


in reply to Re^2: How to complain about changes to a module? (And what good would it do?)
in thread How to complain about changes to a module? (And what good would it do?)

You overestimate my global awareness, but if a subclass, either by you or the author is possible, that sounds like a good way. I had a remotely similar situation with Schedule::Cron::Nofork, where I replaced some functionality with mine, but I think I didn't ever contact the author about changing Schedule::Cron. Eventually, S:C acquired the functionality itself and I should retire my module some day.

  • Comment on Re^3: How to complain about changes to a module? (And what good would it do?)

Replies are listed 'Best First'.
Re^4: How to complain about changes to a module? (And what good would it do?)
by BrowserUk (Pope) on Aug 29, 2008 at 14:41 UTC
    but if a subclass, either by you

    The problem is the maintainers changes should be a subclass of the original module (or a completely different module). And you cannot de-subclass a class. That is, I cannot produce a module that is a subclass of the modified module that removes the added functionality and overhead.

    So the only option for me is to re-release the original code under a new name. Which, besides any other problems with picking a namespace is a pain because the original name and functionality where perfectly matched.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

      But if you can make the case for a subclass and can demonstrate how the subclass would work for the original creator and your current code would still work with the base class, that's a far better position for entering the dialogue than having to say "Your changes suck, back them out." :)

      XXX::Lite?

      Or XXX::Simple? CGI::Simple has reduced functionality of the parent, sans HTML output, amoung other things. And, I believe, it's not built on top of the parent either but a complete rewrite. So in this context, "subclass" is quite a broad definition.

      I use a couple of old versions of modules (DBM::Deep, CGI::Session) because "recent" versions include XS dependancies which aren't currently available (negotiations with webhosters pending). Far from ideal; better would be Lite or Simple versions that were maintained.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://707664]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (3)
As of 2021-02-28 07:37 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?