by stan423321 » Tue Apr 10, 2018 12:54 pm
Retested on the same computer, Windows 10 Home updated to 1709 16299.334, 32-bit to GZDoom 3.4pre-50-g3dd7f17de, 64-bit to GZDoom 3.4pre-55-g80f57dfaf (latest on DRD Team at time of testing).
I don't know ZScript specs by heart, so I don't know if this is a bug being completely fixed, it is however a definite improvement. Both "bad" versions error out with "Script error, "bad.pk3:zscript.txt" line 14:", "Internal error when generating code for array access". Please state whether this is an example of expected behavior (what I would expect first would be mostly identical behavior to the "good" file, but, again, this is no crash at least). The testing file was not changed.
Retested on the same computer, Windows 10 Home updated to 1709 16299.334, 32-bit to GZDoom 3.4pre-50-g3dd7f17de, 64-bit to GZDoom 3.4pre-55-g80f57dfaf (latest on DRD Team at time of testing).
I don't know ZScript specs by heart, so I don't know if this is a bug being completely fixed, it is however a definite improvement. Both "bad" versions error out with "Script error, "bad.pk3:zscript.txt" line 14:", "Internal error when generating code for array access". Please state whether this is an example of expected behavior (what I would expect first would be mostly identical behavior to the "good" file, but, again, this is no crash at least). The testing file was not changed.