7ba8b8f985
This reverts commit
|
||
---|---|---|
.. | ||
antenna.h | ||
battery.h | ||
beacon_array.h | ||
blescan.h | ||
bmesensor.h | ||
button.h | ||
coexist_internal.h | ||
configmanager.h | ||
cyclic.h | ||
dcf77.h | ||
display.h | ||
globals.h | ||
gpsread.h | ||
hash.h | ||
if482.h | ||
irqhandler.h | ||
led.h | ||
ledmatrixdisplay.h | ||
ledmatrixfonts.h | ||
lorawan.h | ||
macsniff.h | ||
main.h | ||
mallocator.h | ||
mobaserial.h | ||
ota.h | ||
payload.h | ||
rcommand.h | ||
readme.txt | ||
rtctime.h | ||
senddata.h | ||
sensor.h | ||
spislave.h | ||
timekeeper.h | ||
timesync.h | ||
vendor_array.h | ||
wifiscan.h |
This directory is intended for project header files. A header file is a file containing C declarations and macro definitions to be shared between several project source files. You request the use of a header file in your project source file (C, C++, etc) located in `src` folder by including it, with the C preprocessing directive `#include'. ```src/main.c #include "header.h" int main (void) { ... } ``` Including a header file produces the same results as copying the header file into each source file that needs it. Such copying would be time-consuming and error-prone. With a header file, the related declarations appear in only one place. If they need to be changed, they can be changed in one place, and programs that include the header file will automatically use the new version when next recompiled. The header file eliminates the labor of finding and changing all the copies as well as the risk that a failure to find one copy will result in inconsistencies within a program. In C, the usual convention is to give header files names that end with `.h'. It is most portable to use only letters, digits, dashes, and underscores in header file names, and at most one dot. Read more about using header files in official GCC documentation: * Include Syntax * Include Operation * Once-Only Headers * Computed Includes https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html