No, it crashes for a different reason.
The first bug occurs if you use pre-increment/decrement with a potential environment variable, such as
. It does not occur in v2, which handles variables the same as if #NoEnv was in effect.
The second bug occurs if you use
, because of an erroneous line
that was added by automatic merge with v1. The heap is corrupted by
, but you may not see the effect immediately.
There is a third bug relating to the first one which affects v1 and v2. If you use
with #Warn, you will get a warning because ++ only looks to the next token for its target variable. Fixing this means delaying the check to a later stage
, which incidentally also fixes the first bug.