On 02.03.2024 15:39, William F Pokorny wrote:
 > The secondary problem is ProcessOptions::IsTrue (and
 > uProcessOptions::IsFalse) use ProcessOptions::Matches which needs the
 > following code at the very top
 >
 >     if ( ((v2[0] == 0) || (v1[0] == 0)) &&
 >         !((v2[0] == 0) && (v1[0] == 0)))
 >     {
 >         return false;
 >     }
 >
 > to not, falsely, test 'true' on empty string options.
Interesting. Then I am not sure this ever worked as documented before in 
the first place: The matches-code is a straight port from 3.1 and 
according to the header there dates back to April 1994. So you probably 
found a 30 year old bug here ...

Thorsten

Post a reply to this message