https://bz.apache.org/bugzilla/show_bug.cgi?id=62904
--- Comment #6 from Yegor Kozlov ---
I checked in a follow-up to my previous commit.
Now all tests pass including the commented ones, that failed in my previous
commit.
Excel has an optimization when evaluating the IF formula: depending on whe
https://bz.apache.org/bugzilla/show_bug.cgi?id=62904
--- Comment #5 from Yegor Kozlov ---
Thanks for the pointer. This commit fixed bug #63054 as well.
The exact change that fixed it was in
TwoOperandNumericOperation#evaluateArray()
We had duplicate pieces of code that evaluated array argument
https://bz.apache.org/bugzilla/show_bug.cgi?id=62904
--- Comment #4 from gallon.fi...@gmail.com ---
@Yegor could you please look into this issue
https://bz.apache.org/bugzilla/show_bug.cgi?id=63054 ?
The topic seems very close, and the divine vision of the code may still be
fresh in your cache.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62904
Yegor Kozlov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=62904
--- Comment #2 from Yegor Kozlov ---
Created attachment 36356
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36356&action=edit
patch to fix evaluation of IF with array arguments
With the attached patch POI evaluates it right.
Summary
https://bz.apache.org/bugzilla/show_bug.cgi?id=62904
--- Comment #1 from gallon.fi...@gmail.com ---
Hello Steven,
thanks for the report.
I encountered the same problem yesterday.
Reasonably enough yet unfortunately, the IF construct is being treated as "lazy
if", and the first argument is evalu
