In POV 3.x, when there is a parsing error, only the code proximate to the error
is displayed.  However, the ultimate cause or the error is often in a different
part of the file, or even a different file altogether.  This is a real problem
if a bad parameter is passed to a library macro.  For example, Round_Cylinder
(-y, y, 2, 1, no) causes a degenerate cylinder error in shapes.inc, but what you
really need to know is which part of your code *called* Round_Cylinder().  It
would be very helpful for debugging if the entire macro call stack is
displayed.

Thank you.

Post a reply to this message