Closed XertroV closed 4 months ago
This is not a bug, and is intended according to the Angelscript documentation:
If a function takes more than one argument, the argument expressions are evaluated in the reverse order, i.e. the last argument is evaluated first.
I would expect this to work correctly (i.e., v2 == v1)
However, I found that
v2 == nat3(v1.z, v1.y, v1.x)
Reading the nat3 like this works:
Is this even a bug? I would have thought arguments were evaluated in order, but doesn't seem like it.
Might be something to report to angelscript forums, but it'd also be a breaking change to fix it if anyone relied on this behavior for some reason.