Syntax check in compiled scripts

[GEOSoft]

I'm just wondering if there is anyway to stop AutoIt from syntax checking a compiled file. It doesn't report anything usefull anyway since it will always report the error at line 0.

I'm not sure how long it takes to do this check on a long script (anything over 5000 lines) but if that time is significant I'd rather it not be done. If there are syntax errors, I should find them at the point where I am testing the script itself.

[Valik]

You're right, you should. The fact that you get a runtime error due to syntax says you're either not using Au3Check on your scripts or you're not thoroughly testing them before releasing them. By the way, how do you expect AutoIt to execute code if it doesn't do at least a basic syntax check to make sure it's valid? We can't very well just blindly assume proper script structure.

[GEOSoft]

You're right, you should. The fact that you get a runtime error due to syntax says you're either not using Au3Check on your scripts or you're not thoroughly testing them before releasing them. By the way, how do you expect AutoIt to execute code if it doesn't do at least a basic syntax check to make sure it's valid? We can't very well just blindly assume proper script structure.

I agree with your points and no AutoIt should not assume that it is a valid AutoIt script. That should have been determined when the script file was tested and again when it's compiled. Then it shouldn't be necessary to check again at runtime.

BTW: Ocassionally I run AU3Check against a script but I always test thoroughly before I try to compile it. The scrip will invariably be tested whenever I make a change to the script so I can catch errors before I add more code into the mix. Even if it's only a MsgBox(4096,'TEST',$A) type of check to make sure that whatever I'm working on is returning the expected results.

Edited December 9, 2006 by GEOSoft