I created the BIPLAN programming language, what do you think about it?

BIPLAN (Byte-coded Interpreted Programming Language) is an experimental programming language based on a recursive descent parser that uses only static memory allocation and operates a completely software-defined virtual machine that does not require a garbage collector. It's human-readable language called BIPLAN is compiled in an 7-bit ASCII virtual-machine language called BIP.

Ciao besn, yes it is designed for constrained environments and now runs only on Arduino compatible devices, although it already supports system calls abstractions to be easily compiled in other environments.

Have you ever used it for a project? Did it help you save time or debugging?

Looks cool! Why is all your code in .h files?

The project looks interesting. I am always a fan of embedded virtual machines. I have some questions after skimming the documentation.

Why do built-in functions use a keyword/operator syntax for arguments, while user defined functions use parentheses? That seems confusing (and was deemed a mistake in python worthy of a decade of pain to remedy.) It would certainly make sense to special case their implementation in byte code for efficiency, but since there's a compilation step, why does the syntax need to change?

Why did you choose to go with Arduino function names? Do you like the camelCasing?

Why is there both a "next" keyword and a "continue" keyword? Don't they basically do the same thing? If the purpose of "next" specifically is to mark the end of scope of the loop, why not use the word "done" or another word that isn't synonymous with "continue"?

If space and efficiency are a priority, and there's a compiler from a higher level language, why did you go with an ASCII-code rather than a true byte-code? That gives you 95 visible characters per byte, which seems to potentially waste 18% or so of program space.