Well, it's just a simple parsing error, so I think the life of this bug should
be quite short.