This is a cosmetic fix only, this bug is present since at least 0.72, but only became apparent since commit 4cebc5af, which made the error no longer silently ignored (v0.72.3). Fixes one of the reported problem of issue #19.
4cebc5af