Commit b127e37e51c21b0a36755dcd19811be931a03d83 wrongly changed two tests, and failed to change a third. One of the two ended up doing: ok ("$ver eq '1,23'", ...); That's always going to succeed as ok() doesn't do an eval; it just looks at the result of the expression, which in this case was a non-empty string. The second test was changed from an 'eq' to '=='. It had this diff: - is ($v, "1.23", "Locale doesn't apply to version objects"); + ok ($v == "1.23", "Locale doesn't apply to version objects"); (The code for is() does an 'eq'.) The is() call is made from within the scope of a "use locale" in which the decimal point character is a comma, but version objects are supposed to always use a dot, regardless of the locale. The == will numify the operands, potentially throwing away the locale's decimal point character. Therefore the test should use an 'eq'. Before these changes, the two tests also didn't do what they purported (and hence the motivation for the changes). The tests previously used 'is()', which is defined in a different file which is outside the locale scope, so that the scalars ($v and $ver) there should have a dot even if they have a comma within locale scope, and hence doing an is() would not catch the bug being tested against. Hence the third test (overlooked in the earlier commit) remained wrong until now.