After having blogged about a bug (and its fix) in Algorithm::CurveFit
, as well as giving a talk about it at the 2024 London Perl and Raku Workshop, I’ve finally gotten around to building and releasing the fix to CPAN.
Last year I wrote a blog post about a fascinating bug I found and fixed in the Perl module Algorithm::CurveFit
. I also gave a talk about this at the 2024 London Perl and Raku Workshop.
As I mentioned in the talk, the bug fix commit landed while I was on the Eurostar train travelling from France to England, which was pretty cool. As it turns out, I didn’t push the commit while actually in the Chunnel, however, that would have been nice, had I thought of it (the internet connection was pretty flaky as it was, so maybe it wouldn’t have worked anyway).
I’d been able to push to the newly-created GitHub repository for the project before LPW 2024 because the Algorithm::CurveFit
author had graciously given me a commit bit to the repository and COMAINT on the Perl distribution in PAUSE. Thanks, Steffen! Thus, all the pieces were in place for me to fix the code and cut a release. So why did it take until January 2025 for a release to appear? Well, work got busy and then there’s this large end-of-year festival every year which tends to take up lots of time.
So, last week I finally found the time to do a bit of housekeeping in the project and to cut a bug-fix release. Get the updated version now at a CPAN near you!1
There are still a few things I’d still like to do as part of a future release:
- Bring the code up to current Perl best practices.
- Investigate and fix the five-point stencil issue I mentioned in my initial article.
- Check more of the code and docs, and do more project-related housekeeping.
Fingers crossed I manage to get around to doing this sometime this year. 🤞
- Ginsu steak knives not included. ↩
Top comments (0)