BloJJ

Adventures of a multidimensional freak

This is Juan Julián Merelo Guervós English-language blog. He teaches computer science at the University of Granada, in southern Spain. Come back here to read about politics, technology, with a new twist

Latest comments

  • Hendo en Riddles in Kafka on the shore
  • TML en Riddles in Kafka on the shore
  • Anonymous en Riddles in Kafka on the shore
  • RonS en Riddles in Kafka on the shore
  • miss en Riddles in Kafka on the shore
  • JJ en Riddles in Kafka on the shore
  • miss en Riddles in Kafka on the shore
  • miss en Riddles in Kafka on the shore
  • Mykalah en Riddles in Kafka on the shore
  • david en Riddles in Kafka on the shore
  • Blogs Out There

    Nelson Minar's Blog
    Jeremy Zawodny's Blog
    Kottke
    Complexes, Carlos Gershenson's blog
    IlliGAL, Genetic Algorithms blog
    Blogging in the wind, Víctor R. Ruiz's blog


    Atalaya, my Spanish language blog
    Geneura@Wordpress, our research group's blog.
    My home page

    Old stories


    Creative Commons License
    This work is licensed under a Creative Commons License.
    Blogalia

    Stats
    Inicio > Historias > Nurturing a Perl CPAN module

    Nurturing a Perl CPAN module

    baby camel and meI 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.

    2010-09-25 10:58 | 0 Comment(s) | Filed in Research

    Referencias (TrackBacks)

    URL de trackback de esta historia http://blojj.blogalia.com//trackbacks/67799

    Comentarios

    Nombre
    Correo-e
    URL
    Dirección IP: 54.91.9.248 (84ce4c9b8c)
    Comentario

    © 2002 - 2008 jmerelo
    Powered by Blogalia