User manual

262
mikoC PRO for dsPIC
MikroElektronika
The preprocessor removes the #include line and replaces it with the entire text of a header le at that point in the
source code. The placement of #include can therefore inuence the scope and duration of any identiers in the
included le.
The difference between these two formats lies in searching algorithm employed in trying to locate the include le.
If the #include directive is used with the <header_name> version, the search is made successively in each of the
following locations, in this particular order:
1. the mikroC PRO for dsPIC30/33 and PIC24 installation folder › “include” folder
2. user’s custom search paths
The “header_name” version species a user-supplied include le; the mikroC PRO for dsPIC30/33 and PIC24 will
look for the header le in the following locations, in this particular order:
1. the project folder (folder which contains the project le .mcpds)
2. the mikroC PRO for dsPIC30/33 and PIC24 installation folder › “include” folder
3. user’s custom search paths
Explicit Path
By placing an explicit path in header_name, only that directory will be searched. For example:
#include “C:\my_les\test.h”
Note
There is also a third version of the #include directive, rarely used, which assumes that neither < nor “ appear as the
rst non-whitespace character following #include:
#include macro_identier
It assumes that macro denition that will expand macro identier into a valid delimited header name with either
<header_name> or “header_name” formats exists.