That thread is talking about how the engine treats conditionals.
The function eval does:
PHP Code:
if ( condition )
return true;
else return false;
And the evalFIX does
PHP Code:
return condition != false;
It's talking about optimization of returns that are inconsistent, because they present two different versions. But... Technically, if something isn't true, it's false... So, if it's not false, it's true. They are two different ways to write the same thing, but they yield different results.
That is NOT what I was asking for.
eval( string ) is a Graal v3 feature that was removed due to security reasons. It was useful because it would execute the code in the string.
It is disabled, but -- If we're on Serverside, this security risk isn't true. I could script my own eval, yes... But that would mean I would have to map out all the operators, set up a parser, and actually parse the information.
This can be done, but it's very prone to flaws. It's much easier to simply use the already created ( but disabled ) version.