Must be. Perhaps my code is wrong somewhere else. I was using this code:
FUNCTION ?opAND(byval quad v1, v2) as quad
' code irrelevant, as it was crashing also with no code here.
end function
This fixed it:
FUNCTION ?opAND(quad v1, v2) as quad
' code irrelevant, as it was fixed even with code here.
end function
Does it matter if it is a macro that is added parameter of ?opAND? I was invoking it like this, i mean, this is the line that was crashing:
IF ?opAND((ISFALSE(area.lng(area.m(x - 1,y + 1), (4)))), (ISFALSE(area.lng(area.m(x,y + 1), (4))))) THEN
This line also had the issue:
IF ?opAND((ISFALSE(GETASYNCKEYSTATE(?VK_Z))), (ISFALSE(GETASYNCKEYSTATE(?VK_X)))) THEN
ISFALSE is a macro:
FUNCTION ?ISFALSEFUNC(byval quad v) as int
if v THEN
return 0
else
return -1
end if
END FUNCTION
MACRO ISFALSE int(r, i t)
quad t = (i)
r = ?ISFALSEFUNC(t)
END MACRO
But it had no issues when used everywhere else.
