Thank you for your thought, Dan. Here are some of mine in return.
I would say that there are several separate things going on here and we'd
benefit from separating them in our discussion. As I understand them,
contract violations are separate from stack traces. A contract violation is
the discover
For the consideration of Robby et al:
The clearest run-time errors I ever received were dumped out of SmallEiffel
/ SmartEiffel in response to contract violations.
These were stack-traces that -- critically -- included parameter values and
local state information for each stack frame. Blame for
You are not the only one to complain :). We've been having an internal
discussion about this, actually.
In this particular, case, I think that you are using provide/contract,
right? If so, the blame really lies with the entire file edf.rkt. So there
really isn't anything more specific to say.
Rob
3 matches
Mail list logo
