Ah yes, trace(). I added this when I was developing Slick-C. It allows me to trace the interpreter itself in a debugger. Place a call to trace() in a macro. Then set a break point in the debugger on the "ptrace_op()" opcode. Then start single stepping the interpreter. Neat trick.
There isn't a way to great way to get the name of the currently running Slick-C function. Currently, the name for static functions is thrown away when a macro module is loaded. However, before run-time there are some context tagging functions that can be used to get the current function name. You can use %\n in an alias to insert the function name in a message maybe for debugging purposes.
