<head><title>ColdC: Function/Method Reference: traceback()</title></head> <body> <h1 align=center><a href="/ColdC/">ColdC</a>: <a href="/ColdC/Functions/">Function/Method Reference</a>: traceback()</h1> <hr> <p> <font size=+1><i>LIST</i> <b>traceback</b>()</font> <p>This function returns the propogated error stack. The first element in the traceback list is the error condition, the second element is what caused the error. The subsequent errors describe the method call stack from the point of origin. <p>The error condition list is ordered as follows: <ol> <li>ERROR code <li>STRING explanation <li>ANY additional </ol> <p>An example of the error condition would be <code>[~methodnf, "$sys.splat() not found.", 0]</code>. <p>The second element (what caused the error) will vary, depending upon where the error came from. If the error came from an operator, function or native method, it is a two element list: <ol> <li>SYMBOL which is one of <code>'opcode</code>, <code>'function</code> or <code>'native</code> <li>SYMBOL what operator, or the name of the function/native method. </ol> If the error originated in a method, this list is ordered as: <ol> <li><code>'method</code> <li>SYMBOL method name <li>OBJNUM current object <li>OBJNUM defining object <li>INTEGER line in method </ol> All other elements are ordered as: <ol> <li>ERROR error code <li>SYMBOL method name <li>OBJNUM current object <li>OBJNUM defining object <li>INTEGER line in method </ol> Keep in mind that the error code will change to <code>~methoderr</code> when it propogates, unless you specifically handle it. See the section <a href="/ColdC/errors.html">Errors</a> for more information. control it <p><hr size=4><p align=center><i>Last Modified on Mar 2 1996</i> <br><i>Copyright © 1995, 1996, Brandon Gillespie</i> </body>