Confusing error message when initializing default argument with undeclared variable

[Bo-Cheng Jhan]

On this example:

; Begin of test.au3
test(1)

Func test($x, $y = $z)
; $z is not declared.
EndFunc
; End of test.au3

This script causes the following error:

test(1)
test(1) ^{ERROR
Error: Variable used without being declared.}

However, it is no "variable" found in this line. The actual problem is in $z, so the following error message will be more readable:

Func test($x, $y = $z)
Func test($x, $y = ^{ERROR
Error: Variable used without being declared.}

[J-Paul Mesnage]

If you use Scite which launch by default AU3Check you get the right line

[Bo-Cheng Jhan]

Replying to Jpm:

If you use Scite which launch by default AU3Check you get the right line

Oh, yes. But I'm used to editting scripts in Notepad and run it by clicking au3 files.
BTW, the compiled exe reports the same wrong line number (line 1).

[J-Paul Mesnage]

The AutoIT compiler and AutoIt have the same code so it is normal that you get the same result

[anonymous]

Shouldn't the compiler/AutoIt3.exe give the correct line number for the error message? If you just run the script, you'd be looking at the line where test is called, and not at the actual line with the error. You shouldn't have to rely on Au3Check to tell you where the error is, AutoIt should tell you that, especially in an uncompiled script.

[jchd18]

You're supposed to run (compiled or not) only syntactically correct programs and this is exactly why Au3Check exists in the first place.
Now suppose the function is only used during yearly inventory: all you have gained in not running Au3Check is spread easy to fix bug(s) in the wild.

The interpretor is not meant to carry the useless code needed to check all issues caught by specific code inside Au3Check.

Other languages have comparable tools, e.g. valgrind, CodeSonar, ... but what you seem to expect is something like clang, which is a much, much bigger project.

[Bo-Cheng Jhan]

Replying to jchd18:

You're supposed to run (compiled or not) only syntactically correct programs and this is exactly why Au3Check exists in the first place.
Now suppose the function is only used during yearly inventory: all you have gained in not running Au3Check is spread easy to fix bug(s) in the wild.

Thanks for comment by jchd18. Actually, I didn't understand functions of other directories and exe in AutoIt3/ before.
I'll survey how to use Au3Check via command line (.bat file) first. I like to compile/run programs by commands, and I feel inconvenience using graphical tools like Visual Studio. However, I appreciate the simplicity of GUI design in AutoIt.