I've been busy lately adding the concept of function calls to my H2D2 programming language. It hasn't
been as hard as I thought, but there has been a reasonable amount of code to write. I have added the notion of
scope as well, so that when a function returns, any local variables go out of scope and the H2D2
virtual machine can free the memory allocated to them. Currently, functions can return a value
(although it's possible in H2D2 to return nothing from a function too) ... but I can't yet pass parameters
to functions, that's on my TODO list, I'll work on that next.
So here is the current test program that I'm using to see if it all works:
repeat (s=s+1 if s<58)
repeat (s=s+1 if s<91)
This program simply outputs some ASCII characters, the result comes out like this:
Simple stuff, but it demonstrates calling the "test()" function like a statement (ignoring the return value)
and also assigns its return value to a variable too. I have also done some work allowing this type of code to be
written out as labelled bracket notation. Essentially I'm treating each function like a seperate program, starting
with its own root node, and then each call to that function simply points to the correct root node. This is how the above program looks if I render the labelled bracket notation generated from the bytecode:
Currently, when I parse the source code, I simply scan for function definitions and emit the code for them
and then go back to a 'bootstrap' node which is the programs entry point. The starting point of the source code is
pointed to from the 'bootstrap' node. It seems to work fine, and it means that programs always execute from node zero (which I'm making sure is always the bootstrap node).
In other news, I compiled H2D2 as a Windows dll, and used Interoperability to call it from C#, this worked a treat and was extremely fast. With the dll version, any output that the H2D2 program creates is returned as a pointer to a string,
so after the program has been run the C# code needs to make an additional call the dll and tell it to free the string containing the output. But, my mandelbrot test program runs in about 200ms this way, since it doesn't have to muck about with writing to the screen. Once the C# program has all the output it can write it in one go rather than a character at
a time, which is much quicker.
Now that I have installed Visual Studio 2012 I might be able to hide H2D2 behind a websocket interface. This should allow for a 'chatty' interface to H2D2 where you can ask it to run programs and get the results returned. This is also on my TODO list :-)