You can clone with
HTTPS or Subversion.
Unfudges for symbols overhaul
Restore hyperop use
Unhack while->, is copy
Unhack for b084a1e
Unhacks for $*OUT, $foo.?meth
FUTURE_Block can be FUTURE::Block now
More hacks, passes ALL TESTS on niecza
More hacks to start running compiler tests
More hacks, can now run code with variables
Enough more hacks to run "say 5"
Various hacks to make yapsi compile under Niecza
Work around junctions, use bug, prompt, $*PROGRAM_NAME in bin/yapsi
[Yapsi] bumped version number
Might as well have it conform to the name of the release.
[doc] updated documents
[Yapsi] added ENTER phaser
And it works! Not bad.
regularize error messages to use "Cannot"
[Yapsi] fix binding var detection
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.
[doc/ChangeLog] [doc/ROADMAP] updated
One could argue that I should have done this before the release.
One would be right. Oh well. Better late than never, I guess.
[t/runtime.t] added failing tests
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.
[Yapsi] bumped SIC version
Between releases, the SIC version is always the version number of the
[t] cleaned up the tests
For the release. Some are actual fixes, some are commentings-out,
but most are fixes to tests that never worked. (do'h!)
[doc/announce/2011.03] still more changes
[doc/announce/2011.03] a few changes
[Yapsi] enabled call before declaration
[Yapsi] implemented subroutine invocation
[t/compiler.t] fixed thinko
Oh, that's why we were doing so well on the errors. Now there's lots of
tests to fix.
[Yapsi] implemented sub declarations
[bin/yapsi] add that newline before exiting REPL
It's very important. Lots of REPLs forget to add it. Yapsi doesn't. :)
[bin/yapsi] slight refactor
Changed sub signature, and the way the prompt looks.
Add a basic REPL
[t/compiler.t] checked error message on failure
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.