Program logic bugs vs input/environmental errors

[bearophile via Digitalmars-d]

luka8088:

> All library code is marked appropriately so when stack is 
> outputted it is shadows out (with gray color) all the lines in 
> library code and point out first non-library line from the top 
> of the stack. In 95% of the time it is the line that the 
> programmer should look into. Other 5% is the time when it shows 
> the line where programmer is forwarding a call to the library 
> but turns out to be ok as it turns out to be much more 
> comprehensible than the entire stack. One note worth mentioning 
> is that juniors have much easier time understanding which lines 
> concern them, and from that I can only conclude that such 
> approach is more intuitive.

This looks like a little enhancement request, to colourize 
differently the parts of the stack trace of the library 
code/runtime from the user code.


> And for exceptions I agree completely with your arguments and I 
> think that there is no need for stack.

I think Walter is not suggesting to remove the stack trace for 
exceptions.

Bye,
bearophile