The catspeak_execute and catspeak_compile_buffer functions are useful, but becomes a bit exhausting for simple "compile-and-execute" use cases, such as loading an initialisation script from a file that only gets executed once.
Consider adding a new catspeak function, which should encapsulate this behaviour:
The second parameter to this function will determine the namespaces to use when resolving global constants. For example, adding a particle function to a namespace:
The
catspeak_execute
andcatspeak_compile_buffer
functions are useful, but becomes a bit exhausting for simple "compile-and-execute" use cases, such as loading an initialisation script from a file that only gets executed once.Consider adding a new
catspeak
function, which should encapsulate this behaviour:If the first argument is not a string, then it is assumed to be a buffer:
The second parameter to this function will determine the namespaces to use when resolving global constants. For example, adding a particle function to a namespace:
and then making that namespace visible to the compiler:
Syntax to be decided.