29-12-2004, 09:39 PM
Based upon what I have seen with tools, most toolsets will flag this as a violation, which is the i9ntent of the rule.
While I have had to use such constructs myself (usually as a result of non-compliant compiler ionstallations and other reasons), using #define in a #include can lead to problems, especially with dependency generation, as I have seen some dependency generation tools not perform proper substitution when generating dependencies.
Hope this helps.
While I have had to use such constructs myself (usually as a result of non-compliant compiler ionstallations and other reasons), using #define in a #include can lead to problems, especially with dependency generation, as I have seen some dependency generation tools not perform proper substitution when generating dependencies.
Hope this helps.
<t>Walter W. Schilling, Jr.<br/>
2004-2005 Ohio Space Grant Consortium Fellowship Recipient<br/>
Uinversity of Toledo PhD Student<br/>
MSES 1998 University of Toledo<br/>
BSEE 1997 Ohio Northern University</t>
2004-2005 Ohio Space Grant Consortium Fellowship Recipient<br/>
Uinversity of Toledo PhD Student<br/>
MSES 1998 University of Toledo<br/>
BSEE 1997 Ohio Northern University</t>