https://github.com/Mr-Monster-0248/Algorithm-interpretor

An algorithm interpretor in C language for the 3rd project in first year at EFREI
https://github.com/Mr-Monster-0248/Algorithm-interpretor

algorithm c code interpreter

Last synced: 3 months ago
JSON representation

An algorithm interpretor in C language for the 3rd project in first year at EFREI

• Host: GitHub
• URL: https://github.com/Mr-Monster-0248/Algorithm-interpretor
• Owner: Mr-Monster-0248
• Created: 2017-03-02T19:41:59.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2017-11-18T15:15:40.000Z (almost 7 years ago)
• Last Synced: 2024-04-24T15:16:20.625Z (7 months ago)
• Topics: algorithm, c, code, interpreter
• Language: C
• Homepage:
• Size: 2.06 MB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• AwesomeInterpreter - Algorithm-interpretor

README

        
C Project: Algorithmic language interpreter 




**This project's aim is to understand the algorithmic language directly in order to be able to implement an interpreter of this language.**

Our project must be able to be compiled on Windows (7, 8 & 10 at least) and Linux (Ubuntu 16.04 LTS and AntiX 16) with gcc compiler.

* To do so, the user who wants to compile the program has to change a #define in constants.h in the headers folder.

* If working with a Windows OS, the user must write `#define WINDOWS` and delete `#define LINUX` (if it was written)

	* If working with a UNIX based OS, the user must write `#define LINUX` and delete `#define WINDOWS` (if it was written)

**EDIT: You no longer need to change the file constants.h to make the program works on both Unix and Windows OS, the program detects the current OS by itself since release 1.1.0**

The executable ExeTest which is provided was obtained by compiling all the sources (.c) files in the sources folder with gcc compiler:

* The exact command used was (located on the project's main folder):


`gcc sources/*.c -o ExeTest -Wall`

* The exact command used to debug out program (with *valgrind*) was:


`valgrind --leak-check=full --track-origins=yes --show-leak-kinds=all ./ExeTest`

------------------------------------------

_If you see any mistake on our code, or a more efficient way to do it, please feel free to leave a message in the "Issues" or "Projects" sections._

Thanks for reading, enjoy exploring the project, or using our program