Just a quick post to announce the DWScript Compendium website!
This is the long overdue language documentation website for DWScript, which Gemini-cli has been patiently building over the last weeks, as it’s wasn’t built as a one-off documentation generation, but as a fully proved and compiled documentation. So hallucinations should be minimal!
At a time when AI are taking over writing code, AI also took over writing documentation.

Every snippet, every example in the documentation compiles (and runs), and the documentation prose was checked against script results and compiler source code. It took weeks to build not just because it ran out of tokens in the free tier, but mostly because I often came back to find gemini-cli stuck or crashed with an out of memory error,…I guess building a long-running cli utility on node.js isn’t a good idea…
However the DWScript WebServer gemini had access to for testing and compiling the documentation never crashed 🙂
Anyways, the doc was completed, along with a dedicated LLM-documentation, in the hope that it will get ingested, and future LLMs will know more DWS syntax… (though TBH, gemini knew it well enough to build the website and the whole testing backend by itself).

Fantastic work, from both LLMs and yourself 😉 Thank you!
A few remarks:
– Source code seems to be empty here: https://compendium.dwscript.net/example/language/bigint_math yet it appears in the full_docs: https://compendium.dwscript.net/full_docs.dws
– The most important missing data for myself, and where I spend most of my time while studying DWScript, is the integration from Delphi’s side: how to register objects/ arrays/methods/units…, how to access script objects content, how call script functions from Delphi, how to transfer data back to Delphi…
Seems to be in cache issue, that example was moved to Math, looks like the backend needs some leftover cleanup 🙂
Documenting integration with Delphi will be next, but it’s much less “safely” automatable for AI-exploration: you need to have it update pas/dfm, and then run a regular executable… which is hard to sandbox unlike scripts. So it will probably be more documentation-from-static-analysis (so hallucinations will be more of a problem)