id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
1750	Au3Check misrepresents undefined Call as critical	anonymous	Jos	"I searched for this issue, but I couldn't find it - even though I've seen it forever.

The Call documentation makes it clear that Call-ing an undefined function is not a critical (exiting) condition, and not necessarily an coding mistake.

However, when using a '''literal''' string for the function name, the Au3Check message implies that it is an coding mistake instead of taking into account that it is a valid operation to acquire the @error/@extended values for in-script handling.

The Call example avoids the issue at hand by using a variable to bypass/workaround Au3Check's conditions.

A modification of the example will prompt the Au3Check Error:
{{{
Call('DoesNotExist')
If @error = 0xDEAD And @extended = 0xBEEF Then MsgBox(4096, """", ""Function does not exist."")
}}}

----

Aside from the actual report, my suggestions toward this specific issue which you can ignore at-will are:
 - Possibly change ERROR to WARNING to reflect the noncritical nature of the condition.
 - Failing that, Document the preference [in a sentence] for function variable/expression passing to evade Au3Check. (like the example shows)  However, to me, it gets silly when you have to add extra code to an already-working script to bypass a message from the code-checker.

Maybe this is a non-issue, but I just think it misrepresents the Call function. I always thought (perhaps incorrectly) that Au3Check should anticipate AutoIt for ERRORs and give anything else helpful as WARNINGs, this seems to diverge from that a bit.
"	Bug	closed		Au3Check	3.3.6.1	None	No Bug