If you, the author, actually need to update the prereqs for your own modules with every release because your own modules fail if they try to use slightly old versions of your own modules, then imagine how painful it must be for people other than you that try to use your modules. Every single time you release a module they have to change their code because your modules lack any useful backward compatibility?
Modules should be modular. That is where the name comes from. Modular code has a defined, narrow interface. Part of the point of the interface being narrow is so that it can also be stable.
You should endeavor to support your own modules being able to work with older (and newer) versions of your own modules. This exercise will help you to better define and to narrow the interfaces that your modules expose.
|Replies are listed 'Best First'.|
Re^4: Checking if your CPAN distributions need to bump their prereq versions (interfaces)
by stevieb (Canon) on Jun 29, 2017 at 21:24 UTC
by stevieb (Canon) on Jun 29, 2017 at 21:47 UTC