Bug 73085 - Function TYPE returns value 8, but that value does not exist in specification
Summary: Function TYPE returns value 8, but that value does not exist in specification
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL: http://docs.oasis-open.org/office/v1....
Whiteboard:
Keywords:
Depends on:
Blocks: Calc-Function
  Show dependency treegraph
 
Reported: 2013-12-28 00:31 UTC by Regina Henschel
Modified: 2020-01-15 09:47 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Some cases with wrong results of TYPE function (14.18 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-12-28 00:31 UTC, Regina Henschel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2013-12-28 00:31:50 UTC
Created attachment 91243 [details]
Some cases with wrong results of TYPE function

The function TYPE returns the value 8 for some cases, see attached file. But the valid values of the TYPE function are given in a table in the specification and the value 8 doesn't exist there.

The help has "Value is a specific value for which the data type is determined. Value 1 = number, value 2 = text, value 4 = Boolean value, value 8 = formula, value 16 = error value." But the specification explicitly states "If a Reference is provided, the reference is first dereferenced, and any formulas are evaluated."
Comment 1 GerardF 2013-12-28 08:33:54 UTC
Excel behaves as Oasis specification:
Value 1 = number, value 2 = text, value 4 = Boolean value, value 16 = error value, value 64 = array. No value 8.

Excel help: "You cannot use TYPE to determine whether a cell contains a formula. TYPE only determines the type of the resulting, or displayed, value. If value is a cell reference to a cell that contains a formula, TYPE returns the type of the formula's resulting value."
Comment 2 QA Administrators 2015-04-19 03:20:25 UTC Comment hidden (obsolete)
Comment 3 Regina Henschel 2015-04-19 21:30:46 UTC
The bug still exists in Version: 4.5.0.0.alpha0+
Build ID: 40b1e8266e47792d354cd457c652bfb0f0a21e69
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-02-11_00:13:43
Locale: de_DE
Comment 4 QA Administrators 2018-07-25 02:41:18 UTC Comment hidden (obsolete)
Comment 5 Regina Henschel 2018-11-06 15:13:36 UTC
The error still exists in Version: 6.2.0.0.alpha1+ (x64)
Build ID: f825e6d4082c0d0beb1c95b881f6a2ee9bfc9161
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-05_00:20:26
Locale: de-DE (en_US); Calc: CL
Comment 6 QA Administrators 2019-11-07 03:35:29 UTC Comment hidden (obsolete)
Comment 7 Regina Henschel 2019-11-07 12:41:01 UTC
The error still exists in Version: 6.4.0.0.alpha1+ (x64)
Build ID: 7c6226bee72805db7f0e567ca9f06c786a7d0da2
CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; 
Locale: de-DE (en_US); UI-Language: en-US
Calc: threaded