[GSoC 2016] Coding phase - First post

Hello all!

As part of the initial stage of the Coding Phase, I had a discussion with my mentor regarding the immediate set of tasks/features to be implemented for the tool (picking from the points highlighted in the proposal). The following are tasks at hand:

1. translator - A system to translate Curry into a format that is suitable for ruby_curry compiler. At the moment we aim to directly translating Curry to JSON if possible with definitional tree information.
2. backtracking - The compiler has a stack based backtracking feature to handle CHOICE in Curry. However this module seems buggy and fails for certain examples.
3. Quality and type system

In addition, I have also added a new test framework to ruby_curry which will enable to integrate all unit tests. This will be beneficial in continously testing the new changes that are being made to the compiler or other relevant modules of the tool.

To integrate all tests, I added a Rake task for tests. All the current unit tests can be run by the rake test command in the base directory of ruby_curry. The commit for this change can be found here.