and set a breakpoint there.
The initial use case is Coco/R parser generated pascal code that analyze a .txt file containing measurement results in text form. In some languages (french) the .txt file has a grammar is not LL(1) and needs quite a bit of debbugging and tweaking of the coco EBNF file description / normalization to be able to inject info in my database.
I don't know where the point I want to BreakPoint will end up in the unit after the generating step, so it is more practical to have a instruction that suspends the execution at the desired point rather than laboriously deleting / re adding break points in the debugger.
The inlining pops'up the stack trace at the line of the call of my local BreakPoint instruction call and one F7 places me on the instruction following the call, what is not to like.