Lucee too rigorous with its type coercion in boolean expressions

Description

Full write-up here: http://blog.adamcameron.me/2015/05/lucee-seems-to-mess-up-boolean.html

Repro:

Expected:

Actual:

The "expected" is based on my own expectations (and requirements, in the given situation), plus ColdFusion delivers on the expectation. As does JS and Python. Groovy matches Lucee's behaviour.

I think Lucee should match CF here. I think it's overstretching itself by doing the full type coercion, as information is lost.

Activity

Show:
Pothys - MitrahSoft
February 14, 2018, 8:52 AM

I've aadded test case for this ticket & confimred that latest version of lucee also acts in same way, It differ from ACF.
will have more input on this & he will confirmed this issue or not.

Pull Request: https://github.com/lucee/Lucee/pull/393

Assignee

Michael Offner

Reporter

Adam Cameron

Labels

None

Affects versions

Priority

Minor