10 Sep
2001
10 Sep
'01
6:44 p.m.
3) Just as stacks of cost centres are useful for profiling, it'd be useful to have stacks of error locations.
The full stack trace is of course highly useful when debugging a library, though. In GHC, you *can* get the stack trace info when an exception is raised ...
Likewise, in nhc98 you can get very useful stack trace info by compiling for tracing (-T) and using the tool hat-stack after the computation crashes. I agree though with Simon that this info probably belongs in the debugging world rather than in the general world of computations. Regards, Malcolm