DDE

NOT EXECUTABLE AS DOCUMENTED, and deliberately recorded as a probe rather than a support claim -- DDE is RTD's twin and takes RTD's treatment. LibreOffice documents it as "Returns the result of a DDE-based link.", whose first argument "is the name of a server application" ("LibreOffice applications have the server name \"soffice\""), whose second "is the complete file name, including path specification" and whose third "is the area containing the data to be evaluated". Every one of those points outside the workbook: the documented behaviour IS the link to another application's live document, and the help's own example makes that concrete -- edit the text in the linked Writer file and "the motto is updated in all LibreOffice Calc cells in which this DDE link is defined". A .xlsx carries no DDE server, and a headless conversion has no application on the other end of the link, so the documented behaviour cannot be reproduced by this harness in any engine. WHAT THE RUN ACTUALLY RECORDED, VERBATIM: this formula returns #N/A on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3). THAT #N/A IS NOT A LIBREOFFICE DEFECT AND IS NOT PUBLISHED AS ONE. It is what a link to an absent server evaluates to, exactly as batch G refused to let WEBSERVICE's sandbox-DNS #N/A become a 'quirky' verdict; the difference is that WEBSERVICE's obstacle was this sandbox's network while DDE's is intrinsic -- no flat file anywhere has a DDE server behind it. This function's LibreOffice cases are therefore declared unverdictable in site/build_site.py (NO_VERDICT_CASES): the executed values are published exactly as they came back, and the engine's Verdict cell reads Inconclusive rather than a support claim in either direction. THE SERVER NAME IS DELIBERATELY BOGUS. LibreOffice's published examples use the server "soffice" -- naming the running office suite itself. This case does not, because a corpus run must not be able to reach out and start or attach to another process; "NoSuchDDEServer" is well formed, is shaped exactly like the documented syntax DDE("Server"; "File"; "Range" [; Mode]), and cannot connect to anything. STORAGE FORM, MEASURED: unlike the rest of group C3, DDE's readable token is the BARE name. All nine candidate spellings (plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE., _xlfn.ORG.OPENOFFICE., ORG.LIBREOFFICE., _xlfn.ORG.LIBREOFFICE., _xlfn.COM.MICROSOFT. and COM.SUN.STAR.SHEET.ADDIN.ANALYSIS.) were round-tripped through all four builds: the plain name evaluates and every prefixed form is #NAME?, and LibreOffice writes the plain name back out unchanged, so harness/xlfn_map.py deliberately has no entry for DDE. The help's DDE section carries no Technical information block at all -- no namespace sentence and no 'available since' sentence -- which is consistent with a name that never needed one. LibreOffice's Spreadsheet-functions help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html. BATCH PROVENANCE (batch J, group C3 of sheets-lo-only-plan.md -- LibreOffice-only and either nondeterministic or context-bound; the final batch of the completeness push). 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 that sentence, and the guard is worth keeping blunt.)

NOT EXECUTABLE AS DOCUMENTED, and deliberately recorded as a probe rather than a support claim -- DDE is RTD's twin and takes RTD's treatment. LibreOffice documents it as "Returns the result of a DDE-based link.", whose first argument "is the name of a server application" ("LibreOffice applications have the server name \"soffice\""), whose second "is the complete file name, including path specification" and whose third "is the area containing the data to be evaluated". Every one of those points outside the workbook: the documented behaviour IS the link to another application's live document, and the help's own example makes that concrete -- edit the text in the linked Writer file and "the motto is updated in all LibreOffice Calc cells in which this DDE link is defined". A .xlsx carries no DDE server, and a headless conversion has no application on the other end of the link, so the documented behaviour cannot be reproduced by this harness in any engine. WHAT THE RUN ACTUALLY RECORDED, VERBATIM: this formula returns #N/A on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3). THAT #N/A IS NOT A LIBREOFFICE DEFECT AND IS NOT PUBLISHED AS ONE. It is what a link to an absent server evaluates to, exactly as batch G refused to let WEBSERVICE's sandbox-DNS #N/A become a 'quirky' verdict; the difference is that WEBSERVICE's obstacle was this sandbox's network while DDE's is intrinsic -- no flat file anywhere has a DDE server behind it. This function's LibreOffice cases are therefore declared unverdictable in site/build_site.py (NO_VERDICT_CASES): the executed values are published exactly as they came back, and the engine's Verdict cell reads Inconclusive rather than a support claim in either direction. THE SERVER NAME IS DELIBERATELY BOGUS. LibreOffice's published examples use the server "soffice" -- naming the running office suite itself. This case does not, because a corpus run must not be able to reach out and start or attach to another process; "NoSuchDDEServer" is well formed, is shaped exactly like the documented syntax DDE("Server"; "File"; "Range" [; Mode]), and cannot connect to anything. STORAGE FORM, MEASURED: unlike the rest of group C3, DDE's readable token is the BARE name. All nine candidate spellings (plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE., _xlfn.ORG.OPENOFFICE., ORG.LIBREOFFICE., _xlfn.ORG.LIBREOFFICE., _xlfn.COM.MICROSOFT. and COM.SUN.STAR.SHEET.ADDIN.ANALYSIS.) were round-tripped through all four builds: the plain name evaluates and every prefixed form is #NAME?, and LibreOffice writes the plain name back out unchanged, so harness/xlfn_map.py deliberately has no entry for DDE. The help's DDE section carries no Technical information block at all -- no namespace sentence and no 'available since' sentence -- which is consistent with a name that never needed one. LibreOffice's Spreadsheet-functions help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html. BATCH PROVENANCE (batch J, group C3 of sheets-lo-only-plan.md -- LibreOffice-only and either nondeterministic or context-bound; the final batch of the completeness push). 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 that sentence, and the guard is worth keeping blunt.)

NOT EXECUTABLE AS DOCUMENTED, and deliberately recorded as a probe rather than a support claim -- DDE is RTD's twin and takes RTD's treatment. LibreOffice documents it as "Returns the result of a DDE-based link.", whose first argument "is the name of a server application" ("LibreOffice applications have the server name \"soffice\""), whose second "is the complete file name, including path specification" and whose third "is the area containing the data to be evaluated". Every one of those points outside the workbook: the documented behaviour IS the link to another application's live document, and the help's own example makes that concrete -- edit the text in the linked Writer file and "the motto is updated in all LibreOffice Calc cells in which this DDE link is defined". A .xlsx carries no DDE server, and a headless conversion has no application on the other end of the link, so the documented behaviour cannot be reproduced by this harness in any engine. WHAT THE RUN ACTUALLY RECORDED, VERBATIM: this formula returns #N/A on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3). THAT #N/A IS NOT A LIBREOFFICE DEFECT AND IS NOT PUBLISHED AS ONE. It is what a link to an absent server evaluates to, exactly as batch G refused to let WEBSERVICE's sandbox-DNS #N/A become a 'quirky' verdict; the difference is that WEBSERVICE's obstacle was this sandbox's network while DDE's is intrinsic -- no flat file anywhere has a DDE server behind it. This function's LibreOffice cases are therefore declared unverdictable in site/build_site.py (NO_VERDICT_CASES): the executed values are published exactly as they came back, and the engine's Verdict cell reads Inconclusive rather than a support claim in either direction. THE SERVER NAME IS DELIBERATELY BOGUS. LibreOffice's published examples use the server "soffice" -- naming the running office suite itself. This case does not, because a corpus run must not be able to reach out and start or attach to another process; "NoSuchDDEServer" is well formed, is shaped exactly like the documented syntax DDE("Server"; "File"; "Range" [; Mode]), and cannot connect to anything. STORAGE FORM, MEASURED: unlike the rest of group C3, DDE's readable token is the BARE name. All nine candidate spellings (plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE., _xlfn.ORG.OPENOFFICE., ORG.LIBREOFFICE., _xlfn.ORG.LIBREOFFICE., _xlfn.COM.MICROSOFT. and COM.SUN.STAR.SHEET.ADDIN.ANALYSIS.) were round-tripped through all four builds: the plain name evaluates and every prefixed form is #NAME?, and LibreOffice writes the plain name back out unchanged, so harness/xlfn_map.py deliberately has no entry for DDE. The help's DDE section carries no Technical information block at all -- no namespace sentence and no 'available since' sentence -- which is consistent with a name that never needed one. LibreOffice's Spreadsheet-functions help page, read live on 2026-08-31 at https://help.libreoffice.org/25.8/en-US/text/scalc/01/04060109.html. BATCH PROVENANCE (batch J, group C3 of sheets-lo-only-plan.md -- LibreOffice-only and either nondeterministic or context-bound; the final batch of the completeness push). 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 that sentence, and the guard is worth keeping blunt.)