1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>#if</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Unreliable Guide To Hacking The Linux Kernel"><link rel="up" href="conventions.html" title="Chapter&#160;10.&#160;Routines and Conventions"><link rel="prev" href="conventions-cplusplus.html" title="C++"><link rel="next" href="submitting.html" title="Chapter&#160;11.&#160;Putting Your Stuff in the Kernel"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">#if</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="conventions-cplusplus.html">Prev</a>&#160;</td><th width="60%" align="center">Chapter&#160;10.&#160;Routines and Conventions</th><td width="20%" align="right">&#160;<a accesskey="n" href="submitting.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="conventions-ifdef"></a>#if</h2></div></div></div><p>
2    It is generally considered cleaner to use macros in header files
3    (or at the top of .c files) to abstract away functions rather than
4    using `#if' pre-processor statements throughout the source code.
5   </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="conventions-cplusplus.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="conventions.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="submitting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">C++&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;Chapter&#160;11.&#160;Putting Your Stuff in the Kernel</td></tr></table></div></body></html>
6