printf() debugging no longer acceptable

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > YOSPOS > printf() debugging no longer acceptable

Shaggar: Apr 26, 2006

Cybernetic Vermin posted:

debuggers could be made a lot more user-friendly really.

tbqh i sort of suspect that beginners would be more likely to use the debugger if you could invoke it with what looks like a function call, like "stopAndInspect(o)" which just breakpoints there, and brings up a nicely explorable watch of the object 'o'. just to remove the modality and often crummy ui of breakpoints from the learning process.

nah, they should just be taught how to use the debugger a little more than not at all. its really not hard to add a break point to a line and then once they figure out that basic stuff they can be taught how to add conditions and watches.

telling them to write code to trigger the debugger is going to create bad habits.

# ¿ Oct 24, 2019 15:08

Adbot: ADBOT LOVES YOU

# ¿ May 16, 2024 09:43

Shaggar: Apr 26, 2006

Zlodo posted:

there are definitely situations when you need a super complicated break condition that you just cant fit into a conditional breakpoint and you can just call DebugBreak() inside of a if instead

maybe but it should be absolutely your last resort and certainly not taught to new programmers.

# ¿ Oct 24, 2019 18:00

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > YOSPOS > printf() debugging no longer acceptable