![]() |
#2 |
Участник
|
Цитата:
There is another way to achieve the same result. You can also insert a no-op line, like i=i; and set a normal breakpoint on that line using F9. This approach has the benefit that only the user setting the breakpoint will hit it – but at the risk of leaving some “silly looking code” behind. In contrast the breakpoint statement triggers a best practice error – so they are easy to clean out again.
Ещё стоит отметить один недостаток ключевого слова breakpoint перед F9. Его нельзя снять в момент отладки. Цитата:
Bonus trick
There is another usage of the breakpoint statement. Sometimes regular breakpoints in forms don’t fire – here the breakpoint statement also comes in handy. Instead of setting a breakpoint using F9 – just type “breakpoint;” in the code. This will trigger the debugger. |
|
|
За это сообщение автора поблагодарили: mazzy (5). |