ERRORTYPE

DERIVED FROM TWO LIBREOFFICE PAGES THAT HAVE TO BE READ TOGETHER, because neither is sufficient alone. ERRORTYPE's own entry in Spreadsheet Functions states the behaviour -- "Returns the number corresponding to an error value occurring in a different cell", "The Status Bar displays the predefined error code from LibreOffice if you click the cell containing the error" -- and gives exactly one example, "If cell A1 displays Err:518, the function =ERRORTYPE(A1) returns the number 518", which is not reproducible from a worksheet formula (518 is an internal 'variable is not available' condition). The CODES are published separately, in LibreOffice's Error Codes in LibreOffice Calc table, which lists 532 against '#DIV/0! Division by zero -- Division operator / if the denominator is 0'. This case and the three below assert that table's codes for the four error conditions a worksheet formula can raise deliberately. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. STORAGE FORM, ESTABLISHED EMPIRICALLY IN BOTH DIRECTIONS BEFORE THIS FILE WAS RUN. A LibreOffice-only function has no OOXML name of its own -- the .xlsx format was frozen on Excel's function set -- so LibreOffice invents one, and this harness must write exactly the token LibreOffice's own .xlsx filter reads. Both directions were measured rather than assumed. IMPORT: every candidate spelling was written into a workbook by openpyxl (which caches no value, so the engine must evaluate from scratch) and round-tripped through `soffice --headless --convert-to xlsx` on all four pinned builds. EXPORT: the same formulas were fed to each build through its own formula parser and written back out to .xlsx, and the stored token was read out of the raw sheet XML. The token recorded for this function in harness/xlfn_map.py is the one both directions agree on across all four builds; the per-function note above says which it is. BATCH PROVENANCE (batch I, group C -- LibreOffice-only functions). This function has x == false AND g == false in docs/data/compat.json: NEITHER Microsoft NOR Google documents it, so this corpus makes no claim about either of those engines, nothing here is measured against their documentation, and the Excel column on the published page reads 'n/a (not an Excel function)' rather than a verdict. The authority is LibreOffice's own help, cited by full URL, by the date it was read (2026-08-31), and by the help version the page serves -- the URLs in this file are pinned to /25.8/ rather than /latest/ so the citation still means this text after the help site rolls forward, and /25.8/ is the help for the newest of the four engine builds the corpus executes. GOOGLE SHEETS: this batch builds the Sheets chunk whose ingest will record presence or absence in that engine. Until that ingest lands, the Sheets column on the published page reads 'Not yet' and nothing in this file claims anything about it. (Stated positively on purpose. scripts/check_honesty.py bans the blanket negative shape of this sentence outright -- it was once a true site-wide claim and is now false for more than 500 functions -- and that guard is worth keeping blunt, so this note carries the same per-function fact in a form the guard does not have to make an exception for.) LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table, which lists 519 against '#VALUE! No value (instead of Err:519 cell displays #VALUE!)' with the explanation 'The formula yields a value that does not correspond to the definition; or a cell that is referenced in the formula contains text instead of a number.' Adding 1 to the string "a" is exactly that second condition. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table, whose entry for 502 is 'Invalid argument -- Function argument is not valid. For example, a negative number for the SQRT() function, for this please use IMSQRT().' The formula in this case is the table's own worked example, so the expected code is as directly published as this function's codes get. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table: 525 is '#NAME? Invalid names -- An identifier could not be evaluated, for example, no valid reference, no valid function name, no column/row label, no macro, add-in not found.' A call to a function that does not exist is the 'no valid function name' arm of that list. This case is also the one that ties ERRORTYPE to the rest of this corpus: 525 is the numeric form of the same #NAME? that every unsupported-function verdict in the dataset is built on. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED FROM TWO LIBREOFFICE PAGES THAT HAVE TO BE READ TOGETHER, because neither is sufficient alone. ERRORTYPE's own entry in Spreadsheet Functions states the behaviour -- "Returns the number corresponding to an error value occurring in a different cell", "The Status Bar displays the predefined error code from LibreOffice if you click the cell containing the error" -- and gives exactly one example, "If cell A1 displays Err:518, the function =ERRORTYPE(A1) returns the number 518", which is not reproducible from a worksheet formula (518 is an internal 'variable is not available' condition). The CODES are published separately, in LibreOffice's Error Codes in LibreOffice Calc table, which lists 532 against '#DIV/0! Division by zero -- Division operator / if the denominator is 0'. This case and the three below assert that table's codes for the four error conditions a worksheet formula can raise deliberately. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. STORAGE FORM, ESTABLISHED EMPIRICALLY IN BOTH DIRECTIONS BEFORE THIS FILE WAS RUN. A LibreOffice-only function has no OOXML name of its own -- the .xlsx format was frozen on Excel's function set -- so LibreOffice invents one, and this harness must write exactly the token LibreOffice's own .xlsx filter reads. Both directions were measured rather than assumed. IMPORT: every candidate spelling was written into a workbook by openpyxl (which caches no value, so the engine must evaluate from scratch) and round-tripped through `soffice --headless --convert-to xlsx` on all four pinned builds. EXPORT: the same formulas were fed to each build through its own formula parser and written back out to .xlsx, and the stored token was read out of the raw sheet XML. The token recorded for this function in harness/xlfn_map.py is the one both directions agree on across all four builds; the per-function note above says which it is. BATCH PROVENANCE (batch I, group C -- LibreOffice-only functions). This function has x == false AND g == false in docs/data/compat.json: NEITHER Microsoft NOR Google documents it, so this corpus makes no claim about either of those engines, nothing here is measured against their documentation, and the Excel column on the published page reads 'n/a (not an Excel function)' rather than a verdict. The authority is LibreOffice's own help, cited by full URL, by the date it was read (2026-08-31), and by the help version the page serves -- the URLs in this file are pinned to /25.8/ rather than /latest/ so the citation still means this text after the help site rolls forward, and /25.8/ is the help for the newest of the four engine builds the corpus executes. GOOGLE SHEETS: this batch builds the Sheets chunk whose ingest will record presence or absence in that engine. Until that ingest lands, the Sheets column on the published page reads 'Not yet' and nothing in this file claims anything about it. (Stated positively on purpose. scripts/check_honesty.py bans the blanket negative shape of this sentence outright -- it was once a true site-wide claim and is now false for more than 500 functions -- and that guard is worth keeping blunt, so this note carries the same per-function fact in a form the guard does not have to make an exception for.) LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table, which lists 519 against '#VALUE! No value (instead of Err:519 cell displays #VALUE!)' with the explanation 'The formula yields a value that does not correspond to the definition; or a cell that is referenced in the formula contains text instead of a number.' Adding 1 to the string "a" is exactly that second condition. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table, whose entry for 502 is 'Invalid argument -- Function argument is not valid. For example, a negative number for the SQRT() function, for this please use IMSQRT().' The formula in this case is the table's own worked example, so the expected code is as directly published as this function's codes get. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table: 525 is '#NAME? Invalid names -- An identifier could not be evaluated, for example, no valid reference, no valid function name, no column/row label, no macro, add-in not found.' A call to a function that does not exist is the 'no valid function name' arm of that list. This case is also the one that ties ERRORTYPE to the rest of this corpus: 525 is the numeric form of the same #NAME? that every unsupported-function verdict in the dataset is built on. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED FROM TWO LIBREOFFICE PAGES THAT HAVE TO BE READ TOGETHER, because neither is sufficient alone. ERRORTYPE's own entry in Spreadsheet Functions states the behaviour -- "Returns the number corresponding to an error value occurring in a different cell", "The Status Bar displays the predefined error code from LibreOffice if you click the cell containing the error" -- and gives exactly one example, "If cell A1 displays Err:518, the function =ERRORTYPE(A1) returns the number 518", which is not reproducible from a worksheet formula (518 is an internal 'variable is not available' condition). The CODES are published separately, in LibreOffice's Error Codes in LibreOffice Calc table, which lists 532 against '#DIV/0! Division by zero -- Division operator / if the denominator is 0'. This case and the three below assert that table's codes for the four error conditions a worksheet formula can raise deliberately. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. STORAGE FORM, ESTABLISHED EMPIRICALLY IN BOTH DIRECTIONS BEFORE THIS FILE WAS RUN. A LibreOffice-only function has no OOXML name of its own -- the .xlsx format was frozen on Excel's function set -- so LibreOffice invents one, and this harness must write exactly the token LibreOffice's own .xlsx filter reads. Both directions were measured rather than assumed. IMPORT: every candidate spelling was written into a workbook by openpyxl (which caches no value, so the engine must evaluate from scratch) and round-tripped through `soffice --headless --convert-to xlsx` on all four pinned builds. EXPORT: the same formulas were fed to each build through its own formula parser and written back out to .xlsx, and the stored token was read out of the raw sheet XML. The token recorded for this function in harness/xlfn_map.py is the one both directions agree on across all four builds; the per-function note above says which it is. BATCH PROVENANCE (batch I, group C -- LibreOffice-only functions). This function has x == false AND g == false in docs/data/compat.json: NEITHER Microsoft NOR Google documents it, so this corpus makes no claim about either of those engines, nothing here is measured against their documentation, and the Excel column on the published page reads 'n/a (not an Excel function)' rather than a verdict. The authority is LibreOffice's own help, cited by full URL, by the date it was read (2026-08-31), and by the help version the page serves -- the URLs in this file are pinned to /25.8/ rather than /latest/ so the citation still means this text after the help site rolls forward, and /25.8/ is the help for the newest of the four engine builds the corpus executes. GOOGLE SHEETS: this batch builds the Sheets chunk whose ingest will record presence or absence in that engine. Until that ingest lands, the Sheets column on the published page reads 'Not yet' and nothing in this file claims anything about it. (Stated positively on purpose. scripts/check_honesty.py bans the blanket negative shape of this sentence outright -- it was once a true site-wide claim and is now false for more than 500 functions -- and that guard is worth keeping blunt, so this note carries the same per-function fact in a form the guard does not have to make an exception for.) LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table, which lists 519 against '#VALUE! No value (instead of Err:519 cell displays #VALUE!)' with the explanation 'The formula yields a value that does not correspond to the definition; or a cell that is referenced in the formula contains text instead of a number.' Adding 1 to the string "a" is exactly that second condition. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table, whose entry for 502 is 'Invalid argument -- Function argument is not valid. For example, a negative number for the SQRT() function, for this please use IMSQRT().' The formula in this case is the table's own worked example, so the expected code is as directly published as this function's codes get. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.

DERIVED from the published error-code table: 525 is '#NAME? Invalid names -- An identifier could not be evaluated, for example, no valid reference, no valid function name, no column/row label, no macro, add-in not found.' A call to a function that does not exist is the 'no valid function name' arm of that list. This case is also the one that ties ERRORTYPE to the rest of this corpus: 525 is the numeric form of the same #NAME? that every unsupported-function verdict in the dataset is built on. Error-code table read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/05/02140000.html. LibreOffice's ERRORTYPE help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html.