#21: Compilation failure from stack inconsistency -----------------------+---------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: closed Priority: major | Milestone: 0.22 Component: compiler | Version: 1.0 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by ehuelsmann):
* milestone: unscheduled => 0.22
Comment:
Part two must have gotten fixed some time, because current trunk does not exhibit this error. There is "unsafe-p" rewriting code in compiler-pass1 which is supposed to address exactly this issue, I've come to understand.
Anyway, closed is not 'unscheduled'; moving to the most recently closed milestone.