those who are wondering.
the '>' separates the individual pseudo-statements.
the first one creates a function called `TestFunction1` that accepts parameters `A` and `B` and outputs `C`.
the second one calls that function passing it the parameters `10` and `11` then the result goes into the variable `TestResult1` (should be 21).
you also might wonder where the separaters are ... well there isn't any.
hypothetically if TestFunction1's result was another function then you could just call it immediately.
this functionality was particularly troublesome when i tried to use the traditional parsing methods, since a label here can be defined and called in 1 go.
tomorrow i will begin to work on actually running the code of #Fauxon , i believe that is normally called 'evaluation'.
the programming might eventually get compiled to binary but for now it will be interpreted, as i don't currently know machine code.
there will also be something like a type checking later but not actually type.
think how an assembly register might work, it doesn't care what the actual type is as long as it's the same size, my variables will be like that 2.
we will statically assign a structure with specific sizes.
then we can accept anything that has the same structure and size.