Since Poki Nanpa is a functional language, everything happens at once. That puts it at odds with most graphical programs, which require a sequence of instructions. The solution is to use the functional aspects of Poki Nanpa to construct a list of instructions, which is then executed in sequence. To pull that off, it needs to be able to handle lists.

In the specification, I have outlined the list operations that will be available in Poki Nanpa. These include adding and removing elements, mapping one list to another using a defined function, and passing the elements of lists as parameters into functions. That also meant coming up with a way to specify whether a function is meant to be evaluated or passed when it is used as a parameter. Right now I’m not sure if the solution I’ve come up with is airtight, which is why it’s time to start implementing the interpreter and finding the gaps and loopholes in the specification.