Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Clark
« on: September 22, 2006, 03:01:09 PM »

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.
Posted by: Dennis
« on: September 22, 2006, 01:59:15 PM »

The name of the function, not really, but the values of it's arguments can be found using arg(n).
Posted by: dmw
« on: July 30, 2006, 02:54:18 PM »

Is there any way to programmatically discover the name of a function and the values of its arguments from within the function itself?

I've found a function enticingly called 'trace' in builtins.e, but I can't figure out what it does, if anything.