Always Correct Correctness Compiler
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
accc
tests
.gitignore
LICENSE
MANIFEST.in
Makefile
README.mkd
Session.vim
info.py
setup.py

README.mkd

Always Correct Correctness Compiler

Python implementation of a very basic langage compiler that never throw errors while compiling. (almost)
Its not a big and complex compiler, and its implementation is something like awful.
Some links are given below.

Errors

The only errors releved by the compiler is :

  • source code contains characters not present in provided alphabet;
  • provided vocabulary don't follow conventions of writing;

If these conditions are respected, whatever you give to the ACCC, it will always return something valid. (but it can be an empty code)

Bias

If compiled source code is too short, or made of lots of repeatitions, some bias can appear:

  • always same values in object code
  • lots of neutral values

The bigger is the vocabulary and bigger is the list of lexems,
the less bias will appear.

Interests

A compilable source code is a string of characters.
Valid characters are provided at Compiler instanciation.

For example, if you have the alphabet '01', any string exclusively composed of '0' and '1' is compilable and will produce something.

Any little modification of the string can lead to heavy or no modification of object code.
In fact, with ACCC you can generate mutation of a source code without problem of compilation error.

Write a code with lots of parameters is another way to do almost the same thing.

Object code

Currently, current object langage is very simple: you can compare things, and do things. That's all. No loops, variables, functions, objects,… Just conditions and actions.

This is an example of code, not totally illogic, created one time with a source code size of 60, the python specification and the alphabet '01':
(indentation can miss)

    if parameter1 == parameter2 and haveThat:
        do_that
        if have_that:
            say_this
            do_that
            if know_that and have_many_things:
                do_that
                say_this
            do_that
        if have_many_things:
            say_this

Please have a look to docstring of Compiler class for more details about that. (notabily used vocabulary)

I/O speaking

Inputs:

  • iterable of characters (doublons are unexpected) that compose the source code
  • vocabulary used for compiling

Outputs:

  • a python (or other, depending of your language specification) compilable code, according to vocabulary

Next improvements

In random-priority order:

  • allow lexems to have arguments;
  • allow configuration of output langage;
  • unit tests;
  • usage example (see tests repertory);
  • base tables on source code instead of only vocabulary;
  • upload on pypi and github (see links below);

Why don't you use…

Someone do the same thing ? Or better ?
Give me the link, i want to see that !

Why do that ?

  1. It's fun
  2. I need it for test something in another project (an Evolution simulation named EvolAcc ; no surprise)

Links