String functions closures incompatibility with ACF

Description

String functions(stringEach(), stringEvery(), stringFilter(), stringMap(), stringSome()) closures have incompatibility with ACF. ACF passes every element as java.lang.Character in closure, which is java.lang.String in lucee. So, that makes an incompatibility with ACF, arithmetic operations and comparison operation which returns different results in lucee than ACF.

https://trycf.com/gist/3bc05e34397e9c807ff526dac02121b2/acf2021?theme=monokai

relates to

Activity

Michael Offner 
9 February 2024 at 09:20

in my opinion ACF is inconsistent here, when i make some tests with ACF i see that ACF sometime handles a character as a number and sometime as a string.

Lucee always handles a character as a string. also in java normally character are not handled as numbers, because there is no need for that, if you wanna handle it as number you translate it to a short or integer.

Saying all that in my opinion this is a bug in ACF and we do not make any bug compatibility to ACF here.

Michael Offner 
5 May 2023 at 08:49

please resolve conflicts and set back to patch ready when done

https://github.com/lucee/Lucee/pull/1495/files

Pothys - MitrahSoft 
21 December 2021 at 15:30

I added a fix to this ticket

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

Pothys - MitrahSoft 
2 December 2021 at 14:34

I added a testcase to this ticket

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

Fixed

Details

Assignee

Reporter

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Priority

Created 1 December 2021 at 09:37
Updated 9 February 2024 at 09:20
Resolved 9 February 2024 at 09:20