WarnAsError or A_Warn variable

[mnaoumov]

I would like to be able to exit the script if any warnings occurred.

It could be done via some flag

Code: Select all

#Warn WarnAsError
#Warn ForceExit

Alternatively, for more control, we could have an automatic variable

Code: Select all

if (A_Warn) {
    ExitApp 1
}

[lmstearn]

Hi @mnaoumov , and welcome.
One possibility is to write the warnings to a file, and run a timer checking the existence of temp.ahk contents:

Code: Select all

FileAppend % "#Warn All, StdOut`na:=b+1", temp.ahk

There's also #ErrorStdOut where, similarly, Log.txt can be checked for zero contents:

Code: Select all

"C:\Program Files\AutoHotkey\AutoHotkey.exe" /ErrorStdOut "My Script.ahk" 2>"Syntax-Error Log.txt"

[nnnik]

This will be the default for AHK v2.
For now you can wrap code you execute in try and throw an exception in the related catch statement.

Code: Select all

Try {
	;your code here
	DllCall("IDon'tExist")
} Catch e {
	Throw e
}

[Helgef]

@nnnik, you can't catch warnings.

I think something like #Warn ForceExit might be useful for v1. I don't think a_warn makes much sense, warnings are for mistakes you don't anticipate.

Cheers.

[nnnik]

Oops - mixed up warnings and errors.

[mnaoumov]

Also, it seems that warning analysis is done during runtime instead of the parsing phase

Code: Select all

#Warn All, StdOut

if (A_Year == 2021) {
    someVariable := variableThatDoesNotExist
}

This code doesn't throw warnings now but will fail in 2021
Warning analysis has to be improved

[Helgef]

Also, it seems that warning analysis is done during runtime instead of the parsing phase

UseUnset (and UseEnv) is not feasible to detect at load time. The other warnings are made during load time. This is documented,

UseUnsetLocal or UseUnsetGlobal: Warn when a variable is read
UseEnv: Warn when an environment variable is automatically used in place of an empty script variable
LocalSameAsGlobal: Before the script starts to run, display a warning for each undeclared local variable which has the same name as a global variable
ClassOverwrite [v1.1.27+]: Before the script starts to run, show a warning for each assignment targetting a class variable

Cheers.

[mnaoumov]

@Helgef thanks, I did not read the documentation carefully. I missed that part of it. However, as a C# programmer, I am used to the idea of as many checks are done as early as possible. That's why this #Warn behavior upsets me

[Helgef]

I see. Note that variables in ahk exist simply by being written anywhere in the script, useunset doesn't warn against using a variableThatDoesNotExist, it warns when you read a variable which haven't been assigned a value. This is not possible to detect at load time, unlike a variable which haven't been declared in a language like c#. Consider,

Code: Select all

F() ? X := 1 : ""
Y := X

You can't know, in generally, what F() will return at load time, so the warning will have to wait until run time, if appropriate.

Cheers.

[mnaoumov]

@Helgef Also what annoys me the most, is the following code doesn't throw any warnings

Code: Select all

myVar := new ClassThatDoesNotExist()

[Helgef]

That, and many other things, have been fixed in v2 (alpha)