Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The <code>&lt;file&gt;</code> include tells the preprocessor to search in <code>-I</code> directories and in predefined directories <strong>first</strong>, then in the .c file's directory. The <code>"file"</code> include tells the preprocessor to search the source file's directory <strong>first</strong>, and then revert to <code>-I</code> and predefined. All destinations are searched anyway, only the order of search is different.</p> <p>The 2011 standard mostly discusses the include files in "16.2 Source file inclusion".</p> <blockquote> <p>2 A preprocessing directive of the form</p> <p><code># include &lt;h-char-sequence&gt; new-line</code></p> <p>searches a sequence of implementation-defined places for a header identified uniquely by the specified sequence between the &lt; and > delimiters, and causes the replacement of that directive by the entire contents of the header. How the places are specified or the header identified is implementation-defined.</p> <p>3 A preprocessing directive of the form</p> <p><code># include "q-char-sequence" new-line</code></p> <p>causes the replacement of that directive by the entire contents of the source file identified by the specified sequence between the " delimiters. The named source file is searched for in an implementation-defined manner. If this search is not supported, or if the search fails, the directive is reprocessed as if it read</p> <p><code># include &lt;h-char-sequence&gt; new-line</code></p> <p>with the identical contained sequence (including > characters, if any) from the original directive.</p> </blockquote> <p>Note that <code>"xxx"</code> form degrades to <code>&lt;xxx&gt;</code> form if the file is not found. The rest is implementation-defined.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload