Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/bugemarvin/monty
https://github.com/bugemarvin/monty
Last synced: 10 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/bugemarvin/monty
- Owner: bugemarvin
- Created: 2022-07-12T07:08:10.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2022-08-01T04:14:57.000Z (over 2 years ago)
- Last Synced: 2024-05-28T16:26:32.831Z (7 months ago)
- Language: C
- Size: 58.6 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# C - Stacks, Queues - LIFO, FIFO
Creating stacks in `C` language Data structures.
#### Usage
```
git clone https://github.com/bugemarvin/monty
```
```
gcc -Wall -Werror -Wextra -pedantic -std=c89 *.c -o monty
```
## The Monty language
Monty 0.98 is a scripting language that is first compiled into Monty byte codes (Just like Python). It relies on a unique stack, with specific instructions to manipulate it. The goal of this project is to create an interpreter for Monty ByteCodes files.
### Monty byte code files
Files containing Monty byte codes usually have the .m extension. Most of the industry uses this standard but it is not required by the specification of the language. There is not more than one instruction per line. There can be any number of spaces before or after the opcode and its argument:
```
julien@ubuntu:~/monty$ cat -e bytecodes/000.m
push 0$
push 1$
push 2$
push 3$
pall $
push 4$
push 5$
push 6$
pall$
julien@ubuntu:~/monty$
```
Monty byte code files can contain blank lines (empty or made of spaces only, and any additional text after the opcode or its required argument is not taken into account:
```
julien@ubuntu:~/monty$ cat -e bytecodes/001.m
push 0 Push 0 onto the stack$
push 1 Push 1 onto the stack$
$
push 2$
push 3$
pall$
$
$
$
push 4$
$
push 5$
push 6$
$
pall This is the end of our program. Monty is awesome!$
julien@ubuntu:~/monty$
```
### The monty program
Usage: monty file
where file is the path to the file containing Monty byte code
If the user does not give any file or more than one argument to your program, print the error message
USAGE: monty file, followed by a new line, and exit with the status EXIT_FAILURE
If, for any reason, it’s not possible to open the file, print the error message Error: Can't open file < file >, followed by a new line, and exit with the status EXIT_FAILURE
where < file > is the name of the file
If the file contains an invalid instruction, print the error message L< line_number >: unknown instruction < opcode > , followed by a new line, and exit with the status EXIT_FAILURE
where is the line number where the instruction appears.
Line numbers always start at 1
The monty program runs the bytecodes line by line and stop if either:
It executed properly every line of the file
It finds an error in the file an error occured
If you can’t malloc anymore, print the error message Error: malloc failed, followed by a new line, and exit with status EXIT_FAILURE.
You have to use malloc and free and are not allowed to use any other function from man malloc (realloc, calloc, …)
Collaborators: Marvin and Samuel