`unlock` function fails on some legit cases
In complex forms of output conditions like (this example), the unlock function will return FALSE when it should return TRUE.
The problem comes from the way the parameters are evaluated, which is sometimes equivalent to transforming the OR conditions to AND.
This bug is critical in the sense it may lock currency units, which become unavailable.
We will need to be careful on this issue, because it will provoke forks on Ğ1-Test. For now it won't provoke any fork on Ğ1, because nobody has ever used a condition with &&
or ||
.
I strongly suggest to put the fix for 1.6.