[
https://issues.apache.org/jira/browse/JEXL-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506302#comment-17506302
]
Henri Biestro edited comment on JEXL-361 at 3/14/22, 3:46 PM:
--------------------------------------------------------------
The test361\{a,b,c\}_3\{2,3\} illustrate the difference in behaviour between
the fix in 3.3 and 3.2. The Engine32 class may be used to 'unfix' and recover
the previous behaviour with 3.3 - for those apps with lots of scripts that
would be too costly to amend.
Commit
[d1c0a05|https://github.com/apache/commons-jexl/commit/d1c0a050e1374f5d7ddf8efba163b11a94a6467e]
was (Author: henrib):
The tes361{a,b,c}_3{2,3} illustrate the difference in behaviour between the fix
in 3.3 and 3.2. The Engine32 class may be used to 'unfix' and recover the
previous behaviour with 3.3 - for those apps with lots of scripts that would be
too costly to amend.
Commit
[d1c0a05|https://github.com/apache/commons-jexl/commit/d1c0a050e1374f5d7ddf8efba163b11a94a6467e]
> Null may be used as operand silently even in arithmetic strict(true) mode
> -------------------------------------------------------------------------
>
> Key: JEXL-361
> URL: https://issues.apache.org/jira/browse/JEXL-361
> Project: Commons JEXL
> Issue Type: Bug
> Affects Versions: 3.2.1
> Reporter: Henri Biestro
> Assignee: Henri Biestro
> Priority: Major
> Fix For: 3.3
>
>
> It appears null may be used as an operator argument despite arithmetic
> strictness.
> {code}
> var i = null;
> if (i < 0) {...}
> {code}
> Should fail when arithmetic is strict.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
