The name implies "no preprocessors in include" but I am not sure if that is what the rule is looking for, or why.
This is a contributed rule and I have accepted it although I was not sure what the rule does. There is an underlying problem of what I should or should not accept, and I do not want any guidelines to solve that problem. What I really want is three rule layers instead of two: now we have "standard" rules (shipped in the Prolint setup) and "custom" rules (only known to you, not available on the Prolint site). I would like something in between: "contributed" rules that are not in the default Prolint setup but can optionally be downloaded from oehive.org/prolint/contribs or something like that. But that would require a restructuring of the registry (rules.d) and of the helpfile locations. That by itself would not be too difficult to make, but would break existing setups if people actually have custom rules.
re: nopprsininclude rule
The name implies "no preprocessors in include" but I am not sure if that is what the rule is looking for, or why.
This is a contributed rule and I have accepted it although I was not sure what the rule does. There is an underlying problem of what I should or should not accept, and I do not want any guidelines to solve that problem. What I really want is three rule layers instead of two: now we have "standard" rules (shipped in the Prolint setup) and "custom" rules (only known to you, not available on the Prolint site). I would like something in between: "contributed" rules that are not in the default Prolint setup but can optionally be downloaded from oehive.org/prolint/contribs or something like that. But that would require a restructuring of the registry (rules.d) and of the helpfile locations. That by itself would not be too difficult to make, but would break existing setups if people actually have custom rules.