Hi jcl,
Could Zorro provide a machine-readable way to retrieve lite-C compiler and runtime errors when started from the command line?
For example:
```powershell
Zorro.exe -run Alice1a -quiet
```
When the script contains a compiler error, Zorro briefly displays the error in its message area and then exits. The diagnostic is apparently not written to stdout or stderr, and the process may still return exit code `0`.
A human can run Zorro with `-stay`, double-click the message area, and copy the error. However, this is difficult and fragile to automate for AI coding agents, build scripts, and CI systems.
Possible solutions:
- Write compiler errors to stderr.
- Return a nonzero process exit code on compilation failure.
- Add an option such as `-errorlog <file>`.
- Always write compiler diagnostics to a predictable text file.
- Provide an option that copies the complete message-window contents to a file before exiting.
Ideally, this command:
```powershell
Zorro.exe -run Alice1a -quiet -errorlog compile-errors.txt
```
would produce error log and terminate with a nonzero exit code.
This would make Zorro much easier to integrate with AI coding agents and automated development workflows. The agent could compile a strategy, extract the exact diagnostic, correct the source, and repeat the test without GUI automation.
Would such an interface be feasible in a future Zorro release?
