Skip to content
New compiler for Lisaac, don't hesitate to comment
C Ruby Shell
Find file
Latest commit 402cda8 Mildred Ki'Lya Fix parser when handling calls/messages to objects
Failed to load latest commit information.
.config Updated ruby tests
bin Call to puts almost ok
config Call to puts almost ok
doc Forget the idea of virtual table
features Fix parser when handling calls/messages to objects
reports Added code coverage for tests
src Fix parser when handling calls/messages to objects
stdlib WIP dispatching, refactor ITM_EXPR hierarchy, implemented Expanded
tools licov: sort the less covered first
.gitignore add cucumber tests
.rvmrc Ruby Gems
BEST_PRACTICES Included BASE_PRACTICES files to work around lisaac compiler's bugs
Gemfile Ruby Gems
Gemfile.lock Ruby Gems
HACKING Testing errors
README More tests Retry Lysaac writen in Lisaac licov improvement Move tests around (cucumber support for subdirectories not as expected)
refactoring.txt Cleanup refactoring.txt Revert "refactoring that do not work well" Added facilities for tests



Lysaac is the rewriting of Lisaac compiler using a better design.

See and


You need lisaac with my release r4 (mildred-r4). See the git repository of
Lisaac at:

The tag is 45093e70b532276233a35eff500299c674e80d51

    object 94e153f61a811226f3eed5109b05ba1b6f97dd5e
    type commit
    tag mildred-r4
    tagger Mildred Ki'Lya <> Fri May 6 12:20:49 2011 +0200
    Release 4, include workarounds that can pass as bugfixes
    Version: GnuPG v1.4.11 (GNU/Linux)
    -----END PGP SIGNATURE-----

You can:

    git clone -b mildred-stable git:// lisaac-compiler

You will also need redo:

If you don't want to install redo, you can always use `tools/do` instead if
`redo` in all the commands.


    redo all


Basically, you need [cucumber]( and rspec, but you can also
follow the guide:

- Install bundler: `gem install bundler`

- Install the necessary gems: `bundle install`

For coverage reports, you'll need the Perl Template Toolkit: ``

Then, just:

    redo tests
    redo coverage

Reports are in the `reports` directory. You can see code coverage.

If you get wierd errors, just `rvm reset`


Something went wrong with that request. Please try again.