A variable declared in a private statement and used in a function but set to nil will throw a undefined variable error if that variable is used as the return value.
This only occurs in scheduled execution space. In non-scheduled execution space this is not an issue.
Execute code seen in this pastebin: http://pastebin.com/BbNhJJFc
This error should not occur. Variables should be able to be set to nil after they are declared and not be removed from the variable namespace.
This is an annoying bug, and very hard to pin down (took me half a day to figure out that it was caused by execution in scheduled space) when encountered by developers because it occurs in valid code.
It is working CORRECTLY in non-scheduled execution! This is the incorrect method of raising this error! Assigning nil to a variable is incredibly important for any complex SQF functionality, especially in dynamic function calling where the return value may be different all the time and returning nil from an inner function is desired.
Confirmed.
In the meantime, this can be used as a work-around:
if (isNil "_var") then
{
nil;
}
else
{
_var;
};
I just removed all but one spawn in ACRE2 haha. Everything except about 10 lines of code runs in non-scheduled events now (was pretty much already there though before this bug, scheduler space is evil).
Indeed pretty strange behaviour. Easy repro:
a = call {nil}; hint str [a]; //[any] - fine
even more simple
a = nil; hint str [a]; //ok
This bug also occurs in NON-SCHEDULED code when executed from the "action" parameter in dialog button controls!