laughinghan/mathquill — comment on commit d4ded2cd815d57d1d9c6272690c1366b6bc135b8
File:  line 0
By laughinghan:

bored in lecture, exceptions came up, occurred to me to test this. Turns out you're not wrong, but I'm still right. Web Inspector (in Chrome) actually has two pause-on-exception modes: "Pause on uncaught exceptions." and "Pause on all exceptions." You can see what the difference means by trying it out: open Web Inspector, make sure to pause on exceptions, and click the button http://jsfiddle.net/eD38J/

So yes, you can still debug things, because it's possible to pause where the exception is first thrown, but it still makes debugging a good deal more annoying, because it's not possible to do that but only if the exception is rethrown, which means when debugging we'll either pause in `Range::each` a lot when the error is actually being thrown elsewhere, or we'll be pausing on a bunch of meaningless exceptions that are caught and not rethrown, like any code that tries to break out of an `each` by `throw`ing `break`.