> Now that you know that, you'll never try to breakpoint a comment again.

Well, so far this has tripped me over at least 17 times since I 
discovered what the problem was.

> In a year from now, when people bitch about how crappy the debugger is,
> you'll say "works for me! Must be your problem."

I can't believe that such a trivially fixable issue isn't fixed... In 
fact, I can't believe that nobody caught this in testing. When you fire 
up a debugger with support for breakpoints, literally THE FIRST THING 
you're going to do is try to stick breakpoints on top-level functions. 
How did this miss this?!

The next thing, of course, is that if I put a breakpoint on line 137, I 
now have to guess whether that means execution halts *before* line 137 
runs or *after* line 137 runs. In any normal debugger I could just put 
the breakpoint on line 136 or line 138 (assuming they're empty), but nooo...

I really can't believe somebody would go to the extreme lengths required 
to build something as complex as a debugger, and then release it while 
it's trivially broken. I mean, the effort to fix this glitch compared to 
the effort of developing the debugger in the first place...

Anyway, I guess none of this is going to fix my algorithm. I suppose 
it's a miracle that you can debug JavaScript at all. But *damn*!

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message