Debugging and PURE procedure cascade

[everythingfunctional]

I like the idea. I did try this once and had at least one compiler still complain about the call to the impure procedures because they were still in the same file (i.e. it could see their actual interfaces), but maybe there was something different from the way you’ve got it here.

[everythingfunctional]

I do have one suggestion/request though. You should put a big bold disclaimer that “Use of this library is not standards conforming and you can expect things to break in plenty of situations. It should be used only for debugging purposes.”

[Ali]

@everythingfunctional

I do have one suggestion/request though. You should put a big bold disclaimer that “Use of this library is not standards conforming and you can expect things to break in plenty of situations. It should be used only for debugging purposes.”

Thanks for your suggestion. I added your sentence to readme.

@everythingfunctional

I like the idea. I did try this once and had at least one compiler still complain about the call to the impure procedures because they were still in the same file (i.e. it could see their actual interfaces), but maybe there was something different from the way you’ve got it here.

I tested ForDebug on my Linux system with ifx, ifort, nvfortran, and gfortran, and there were no issues. Additionally, there is a CI test with gfortran and ifort on Windows and linux that also encountered no problems.

[everythingfunctional]

Glad it works. Just thought I’d mention it in case.