Bug 91605 - Automatic type conversion of text to number failing applyed to array under "iterative" evaluation
Summary: Automatic type conversion of text to number failing applyed to array under "i...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-25 10:06 UTC by Wolfgang Jäger
Modified: 2015-11-28 16:39 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Demonstration mentioned in the bug description (72.33 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-05-25 10:07 UTC, Wolfgang Jäger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Jäger 2015-05-25 10:06:10 UTC
http://ask.libreoffice.org/en/question/51087/array-formula-calc-4432/
The above URL will open a forum thread dicussing the issue rather detailed. It is, however, independent of the fact that the original question referred to an example gotten from an XLSX file.

In short:
A range containing texts (strings) syntactically acceptable as numbers should automatically convert to numerical values if used as an operand of an arithmetic expression. (Delimitation may be problematic.)
This does not reliably work under the condition of iterative array evaluation as specified in the relevant OASIS document (http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.html#__RefHeading__1017866_715980110 ), num "2)". 
#A The output range will show the #VALUE! error. 
#B The same error will be returned by a function trying to evaluate a parameter containing the array expression.

Versions
I tried this with V4.4.3, prerelease 5.0.0.0 beta1 and got the results as described and demonstrated by the attached example.

I also tried with some older versions ('Portable') I have access to. V4.1 and the older ("legacy") versions also showed the error, but with the exception of case #B.
Comment 1 Wolfgang Jäger 2015-05-25 10:07:46 UTC
Created attachment 116007 [details]
Demonstration mentioned in the bug description
Comment 2 Buovjaga 2015-06-08 11:03:19 UTC
(In reply to Wolfgang Jäger from comment #1)
> Created attachment 116007 [details]
> Demonstration mentioned in the bug description

Confirmed.

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: be8512f99bc9ab18e55aabe01cc0ab1e6baea9e6
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-08_05:58:40
Locale: fi-FI (fi_FI)
Comment 3 Wolfgang Jäger 2015-11-28 15:37:36 UTC
Bug in the attached example no longer showing under V5.1.0.0Beta1.
It was still showing up under V5.0.3.2.

Can someone confirm my statement and update the Status, please?
Comment 4 Buovjaga 2015-11-28 16:39:10 UTC
Yep, confirmed it is ok now.

Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+
Build ID: a7c3a2a9be83686657c06f37d521f9f6d2004ddd
Threads 4; Ver: Windows 6.1; Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2015-11-28_04:39:18
Locale: fi-FI (fi_FI)