mellab / monty

0x19. C - Stacks, Queues - LIFO, FIFO

Usage

• Clone the repository

$ git clone https://github.com/mellab/monty.git

• The code will be compiled this way:

$ gcc -Wall -Werror -Wextra -pedantic *.c -o monty

• The monty program

$ ./monty <file.m>

Tests

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:

push 0$
push 1$
push 2$
  push 3$
                   pall    $
push 4$
    push 5    $
      push    6        $
pall$
vagrant@vagrant-ubuntu-trusty-64:~/0x19-stacks_queues_lifo_fifo

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:

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!$
vagrant@vagrant-ubuntu-trusty-64:~/0x19-stacks_queues_lifo_fifo$