I have just uploaded the latest version of Algorithm::Evolutionary
, a library I use all the time for doing stuff with evolutionary algorithms; latest one online being this poster
accepted at the GECCO evolutionary computation conference
However, it can be left alone for long stretches of time, which means that, when I come back to it, the language and upstream modules I use have drifted and it can be absolutely obsolete. This happens all the time: Perl and CPAN are living beings, and a module left to its own devices plainly stops working after some time, due to an API change or some borderline condition that is no longer accepted in current versions.
That's why you have to stop, every six months or so, to run tests all over again; or check CPAN testers
to see if something's gone wrong and fix it. Of course, sometimes there can be documentation errors, problems you hadn't covered by your tests, and so on. And the plain fact that after six months, all code written by you looks alien. So my advice is to go back to whatever you did from time to time, see how it's doing, and nurture it. It can't hurt to do a maintenance release, either.