is this a known issue? considering the following code, acf 2025 resolves the ternary different than every other engine

bob = 0;
writeOutput(val(bob) ? " <strong>truthy</strong> " : " <strong>falsy</strong> ");
if ( val(bob) ) {
    writeOutput('<strong>i am true</strong>');
} else {
    writeOutput('<strong>i am false</strong>');
}

any other (cf, lucee, bx) = falsy i am false acf 2025 = truthy i am false https://trycf.com/gist/8f25f265335cdf90c03c28d79d951227/acf2025?theme=monokai

Trycf isn't feeling well ATM, but that certainly seems wrong!

@Matt Jones this looks like a bug I reported a while ago (CF-4225874)

@bdw429s, i tested against bx, all versions of lucee and cf 2018 and up. 2025 was the only one that acted dumb, and only if my compare was val(bob) if i ran without the val(), bob it behaved as expected.

@Matt Jones: This seems to be the same issue that @bockensm has reported, I have shared a patch for this in DM. Kindly apply the patch and see if it works. You can also download the patch from https://tracker.adobe.com/#/view/CF-4225874

@Ashudeep Sharma thank you, that patch does appear to resolve what i was seeing.

I love how we share!!! This was driving me crazy last night running thru some CF2025 checks as this was not working properly. Now I just need to deal with the CFMX_COMPAT removal.

writeDump( val( form.value ?: 0 ) ? true : false );

@jc another alternative, before it makes it into an update, if you can't apply the hotfix jar from CF-4225874 this also works writeDump( val( form.value ?: 0 ) != 0 ? true : false );

@jc: Yes this bug has been targetted and the fix will be available in the next bugfix update.

Thanks @Matt Jones, I had no issues applying the hotfix, just wanted to confirm it was slated for the next bugfix. Thank you for the update @Ashudeep Sharma