I prefer quantifier + as a postfix without whitespace. :)
Make yapsi work again
… warning in runtime.t
Might as well have it conform to the name of the release.
And it works! Not bad.
In generating the SIC for a binding statement, detecting whether the rhs was a variable used to be tricky business. With FUTURE it's dead simple. This accidentally makes nested subroutine declarations work.
One could argue that I should have done this before the release. One would be right. Oh well. Better late than never, I guess.
For some reason, this doesn't work yet. It dies with the error "Trying to invoke a non-closure", for no reason immediately obvious to me.
Between releases, the SIC version is always the version number of the upcoming release.
For the release. Some are actual fixes, some are commentings-out, but most are fixes to tests that never worked. (do'h!)
Oh, that's why we were doing so well on the errors. Now there's lots of tests to fix.
It's very important. Lots of REPLs forget to add it. Yapsi doesn't. :)
Changed sub signature, and the way the prompt looks.
Just knowing that something fails isn't very informative. It turns out we were sometimes failing for the wrong reasons. This commit is more discerning about the actual failure.
Instead of a lexical inside ::Actions, it is now a private attribute. This makes a lot more sense, because the variable should be reset with each new parse anyway.