Add the mapping function to rules

Description

Prepare 0.1.0 release to make zen-parser usable on my another project.

Tasks

• Make correct errors throwing 🕒 1.0
• Remove typo bug in isMachinDone 🕒 0.1
• Refactor things 🕒 1.0
• Update Readme 🕒 0.5

Error: Parsing Error expected $, semicolon, but got equal, at 27,expected $, semicolon, but got equal, at 27

Create a GLR parser table generator

I can't see the way to do it now. It seems like it's impossible with current parser organization to say what's an error.

My suggestion is: if no rules full match and no rules part match - there is a mistake.

Make every rule cacheable with state handling like this:

match: {
  cache: (function () {
    let state = 'nope';
    return function (token) {
      if (state === 'nope' && token.type === 'fist-token-in-grammar') {
        state = 'first-token-found';
        return 'part';
      } else { ... }
    };
  })()
}

and remove other modes, let's make only stream mode

Better we do it like stream mode

So we just take a symbol and do the same as we did for grammar

Problem

  [ 
    rule(['word', 'function-definition', 'raw'] ... ),
    rule(['word'] ... ),
  ]

Anyway whatever algorythm we choose, one of those rules will never apply.

Solution

We can extend rules to take N next tokens. And we can add recalculation.

Better solution

Switch to GLR algorythm.

Only the rest field in the result may be replaced by mapping. I need to include the type field inside resulting expression

Create a GLR parser

Remove non terminals from syntax error output.

For this we need to rework lexer to make terminals accessible from parser

Description

Prepare a full stable release for zen-parser

Tasks

• Add Stream Mode support

It should support:

• movement commands
• paint/unpaint
• function definitions (with parameters)
• cycles
• branching
• variables
• walls checking
• cycles break
• returns
• is checking (==) and > and < and >= and <=
• bool and string and number types
• comments

For example:

down
while wall on the bottom and not wall on the right
  right
  paint
down
paint

if wall on the left
  return

declare goUntilWall (direction) ->
  if direction is 'right'
    while not wall on the right
      right

Remove examples from npm package

I think I can compare it to jison on some synthetic examples e.g. Jade, HTML, JSON, brainfuck and Thue

• Test across those langs
• Test with errors
• Test with big auto generated data