>I disagree with you on COMPILE command. It's good that it doesn't interact with user. The errors, if any, are looged into .ERR file. This way you have control on what to do in each case.
>

I have not written well my thought.

Of course, COMPILE it doesn't have to interact with the user,
but it has to produce an error that the application has to be able to manage (TRY/ENDTRY...);
the file ERR is not enough.

>>CTRL+E is a DO shortcut, it compile the file with a COMPILE command.
>>COMPILE command doesn't interact with the user,
>>and this can to be "by design" into a full dynamic language as VFP,
>>but if this is the design choice, it is wrong,
>>because it create a difference among COMPILE and EXECSCRIPT.
>>At design time this is a minor issue, but at runtime this can to generate side effects,
>>because COMPILE and/or DO execute the correct code, and generate errors inside the compiled code,
>>execscript require a perfect syntax code to execute the first line.
>>
>>EXECSCRIPT is correct for me,
>>and backward compatibility it is not a good reason to keep on being wrong.
>>
><snip>