This is an example. The include file is managed by another program and if soem condition is defined in that, I like to pause the compile in the middle so the user can do a task and then continue.
I'm not sure what kind of task the programmer can do at that point... (other than getting a cup of coffee
)
But I get your point.
The problem is that compiling is an internal process in Lazarus, so there is no interaction with the user during compiling.
You can look at the NOTEs in the messaging window after compiling (including with all the other errors, warnings and hints).
You can also put {TODO: custom_task} inside code where you need to still do some stuff.
View > ToDo List will give you all tasks in your project.
But that's different from pausing the compile process (which is AFAIK not possible in Lazarus).