Persistent bug in CodeSnip re-squashed, properly this time?
It had to happen didn't it? Not long after my post about yesterday's bug fix release of CodeSnip, Oliver reached out to point out a potential problem with the way I'd implemented it. See the linked post and comments if you're interested in the details.
Suffice to say that the problem was sufficient for me to hunt for an alternative solution. Having found one I've rushed out hotfix v4.24.2 to patch yesterday's release (v4.24.1) and make it more robust.
Whether or not you downloaded yesterday's you really should update CodeSnip to the hotfix release.
⮞ Get hotfix release v4.24.2 from GitHub.
The fix involves a dirty hack of which I'm deeply ashamed, but it works. To be up-front about how horrible this hack is I've liberally sprinkled comments that include the text "!! HACK" in the code. Also, any new methods and fields that implement the hack have names prefixed with _HACK_.
I need to get this patch out, so don't have time to explain the solution here. See yesterday's post for a statement of the problem and an overview of the fix in v4.24.1. If you're interested in today's fix the following two diffs should help:
- Diff between v4.24.0 and v4.24.2 - shows the fix relative to the last release containing the bug, without any of the reverted changes from v4.24.1 cluttering things up. Ignore all the documentation, version and help file changes.
- Diff between yesterdays fix, v4.24.1 and today's fix, v4.21.2 - shows what changed between the two fixes. Ignore the documentation and version file changes.
Comments
Post a Comment