A Common Lisp Interpreter Built in COBOL.
This is a small project built by a student at the Recurse Center to express a love for COBOL and better understand it.
Due to COBOL's lack of functions and recursion, the recursion required for Lisp is built from the ground up using file processing. Also, due to the lack of a widely supported debugger, a system logger was also implemented.
Please note that Cisp is currently only actively developed for Windows. *Nix users may experience issues.
All features are currently in development. This is a list of what is to come.
The README much like the entire project is in current development.
- Make a subdirectory for your lisp file.
- Create a new file
helloworld.lispin your subdirectory containing the following:
- To run Cisp cd into the bin (Note that you must cd in)
- Run Cisp
Currently the COBOL source files are located in the root directory.
- bin - Contains all necessary *.dll's (windows users) for those who want to play with CISP without changing the code. This is due to the fact that so few people have COBOL compilers.
- logs - Contains the log file generated by the system.
- test - Contains all test files organized by subject.
- cisp.cbl - The main COBOL program.
- cisp-error.cbl - The Error System in the program. It will "throw" errors when called.
- lisp.cbl - Responsible for executing the lisp program.
- logger.cbl - The Logging System in the program. It will log events in the system when called.
- recursion.cbl - Handles recursion as requested from lisp.cbl.
- tokenizer.cbl - Responsible for tokenizing the lisp file given to execute.
To run all tests in the project, double click
To run a single test:
Create your own Lisp Files for Testing
- Create a directory in
test\to create another test category.
- In your subdirectory create a lisp file.
Instructions yet to come. The author is a window's user, and *nix systems are not currently supported.
A high level overview is to compile the project and run the executable in the bin folder.
How Cisp Works
Log to Log File
Throw an Error