Thanks for the IPC docs. Two observations from testing 7.20.0 x64 on Windows 11, and one question.
1. afl_execute error format. The two examples in the doc differ from each other (error_code "1" with "Error 30. Syntax error. Line 3, Column 15." in the afl_execute section, error_code "29" with "Syntax error. Line 1, Column 11." in the Example Session), and the build returns a third form. Sending a deliberately broken formula (closing parenthesis and semicolon left out on line 1):
```
x = MA( Close, 10
y = 1;
```
returns:
```
{ "error" : "'afl_execute' command failed.", "error_code" : "1", "result" : "\nx = MA( Close, 10 \ny\n^\nFile: 'unnamed', Ln: 2, Col: 1\nError 31.\nSyntax error, unexpected IDENTIFIER, expecting ')' or ','" }
```
So error_code is "1" for every compile and runtime error I tried (Error 10, 16, 30, 31, 42), and the AFL error number, line and column are only in the result text. Is this the format that will stay, so a client can rely on parsing "Ln:", "Col:" and "Error N." from result?
2. #include under remote execution. With the AI switch on, fopen, fdelete, ShellExecute and InternetOpenURL are refused with "The formula comes from untrusted source. Can't execute this function". #include is not refused; it is resolved against the Formulas\Include folder. Mentioning it in case it belongs on the blocked list.
3. Question: is there a way for afl_execute to only compile (syntax check) without executing? My use is checking AFL for errors before it goes on a chart.
As always - thank you!!
Peter