Comment by jashkenas

Oof. Embarrassingly enough, I just bumped us to 1.3.1 -- there was an overly-strict patch that would prevent compound assignments to undeclared global variables, like this:

    global.value or= 1

... which should now compile properly as expected.