Nesting Include Files is not difficult to maintain

The rule “nonestinc” provides a warning if you are including a include file within another include file (nesting include files).
The Risk:
When you have multiple levels of nested includes, the maintenance of programs becomes increasingly difficult. In addition, you can start constructs in one include file and end them in another. Imagine starting a transaction in include A, then ending it in include D. Are you even aware that you are in a transaction during includes B and C?
How to solve this:
Best answer: reorganize your program for maintainability.

How to suppress these warnings:
You can put the directive {&_proparse_prolint-nowarn(nonestinc)} directly before the embedded include line. See also: suppress warnings.