3 ms·
I'd say that except some heavily multithreaded cases, then print approach may be due to lack of mature tooling I can't understand why would anyone prefer to wr
by tester756 6y ago
I'd say that except some heavily multithreaded cases, then print approach may be due to lack of mature tooling
I can't understand why would anyone prefer to write some print, when you can have Visual Studio's
* break point
* conditional break point
* ability to place another break points when you're already on the other
* expression evaluation at fly!!
* decent possibility to modify code at fly
I still remember case where I modified function with line with bad SQL (breakpoint after executing this SQL), added call to the same function with the same parameters after this breakpoint, let it execute again, caught the breakpoint once again and removed that call to itself
and all of that without recompiling program! it felt like magic
- username90 6y agoPrint statements lets you see many things at once. Breakpoint only breaks at one thing. They are good for different things.
- tester756 6y ago> Breakpoint only breaks at one thing. One breakpoint breaks at one thing, that's why you can have many of them
- username90 6y agoBut it only stops at one thing at once. With print debugging I can print 100 things in different places and look at all of them at once giving me a temporal overview, I can't do that in a debugger.