pauwell / chip8-script Goto Github PK

Most important functions:

lel

Crashes when the corresponding endif or endfor are missing.

if-conditions without any statements in the body messes up the parsing process without showing any errors.

👎

E.g the following compiler test will fail when doing the token to AST parsing:

c8s::test_compiler(
	" {1} Full set of commands",
		
	"VAR a = 4\n"\
	"IF a == 4:\n"\
	"	VAR b = 8\n"\
	"ENDIF"
);

Remove the loop variables from the variables list to make space.

Change it to:

namespace no_indent
{

void foo_no_indent()
{
    std::cout << "hi";
}

}

if-conditions without any statements in the body messes up the parsing process without showing any errors.

👎

The following test fails:

c8s::test_compiler(
        " {1} Full set of commands",
		
	"VAR a = 4\n"\
	"IF a == 4:\n"\
	"        IF a != 4:\n"\
	"        ENDIF\n"\
	"ENDIF"
);

FIX

Loop exit-conditions are only tested for equality not greater or less then.
This can result in an infinite loop if e.g: FOR i=5 TO 10 STEP 2 '(i: 5,7,9, 11 ! )

This can be intended behavior..

The following is an idea on how to implement if-conditions and for-loops:

Dealing with if-conditions (if a==b ):

if a==2: // 5XY0 Cond if(Vx==Vy) Skips the next instruction if VX equals VY.
NOT TRUE // 1NNN Flow goto 123; Jumps to address NNN.
TRUE // 1NNN Flow goto 345; Jumps to address NNN.
123 NOT_TRUE:
345 TRUE:

Dealing with for-loops (for i=0 TO 10):

Requires:

v[x] = 0
v[y] = i-max(10)

How it works:

1. [Loop expression]
2. v[x] += 1; // Inkrementiere V[x]
3. 5XY0 // V[y] muss i(max) beinhalten
4. GOTO 1