Tuesday, June 05, 2012

When a Hotfix Requires a Hotfix

Do you know that feeling when you can’t put together a simple piece of code? You turn it around and around and there’s always “one last” problem. Even after you’ll happy with it, the first user that tries it out will find a problem. And then you correct that and you’ll happy with it again and the first user that tries it now will find a new problem. :(

It looks like I’m playing this game with Parallel.Join. I can’t make the @#$%^ thing to work correctly. That’s why I have just issued another hotfix. If you are following the SVN head, just do the Update. Otherwise, please download the updated OtlParallel unit.

Thanks go to [meishier] for reporting the problem!


  1. I think I know exactly what you mean :)

  2. Anonymous22:02

    Isn;t that what the testing phases (Alpha & Beta) are for ?

    1. Of course they are - but nobody caught it then. Or in the 3.0 release. Obviously, Parallel.Join is not used much.

  3. Anonymous22:33

    http:// deviq. com/duct-tape-coder

  4. The real problem is when a hotfix is needed and there is none... Better more hotfixes than more remaining bugs !

  5. Simple does not always means easy.