ESP32-PaxCounter/include
Christian Ambach 4cab5113ca Revert "SPI code added (experimental)"
This reverts commit 16759c4dd5.
2018-11-02 12:09:12 +01:00
..
antenna.h Code Sanitization 2018-10-14 13:26:23 +02:00
battery.h Code Sanitization 2018-10-14 13:26:23 +02:00
beacon_array.h Code Sanitization 2018-10-14 13:26:23 +02:00
blescan.h Code Sanitization 2018-10-14 13:26:23 +02:00
button.h Code Sanitization 2018-10-14 13:26:23 +02:00
configmanager.h Code Sanitization 2018-10-14 13:26:23 +02:00
cyclic.h Code Sanitization 2018-10-14 13:26:23 +02:00
display.h Code Sanitization 2018-10-14 13:26:23 +02:00
globals.h project migrated to arduino LMIC 1.6 MCCI 2018-10-21 19:00:20 +02:00
gpsread.h project migrated to arduino LMIC 1.6 MCCI 2018-10-21 19:00:20 +02:00
hash.h Code Sanitization 2018-10-14 13:26:23 +02:00
irqhandler.h Code Sanitization 2018-10-14 13:26:23 +02:00
led.h LED control improved 2018-10-24 18:07:41 +02:00
lorawan.h Code Sanitization 2018-10-14 13:26:23 +02:00
macsniff.h Code Sanitization 2018-10-14 13:26:23 +02:00
main.h LED control improved 2018-10-24 18:07:41 +02:00
ota.h project migrated to arduino LMIC 1.6 MCCI 2018-10-21 19:00:20 +02:00
payload.h Code Sanitization 2018-10-14 13:26:23 +02:00
rcommand.h call LMIC_shutdown before ESP.restart 2018-10-17 07:10:37 +02:00
readme.txt Code Sanitization 2018-10-14 13:26:23 +02:00
senddata.h Code Sanitization 2018-10-14 13:26:23 +02:00
spisend.h Revert "SPI code added (experimental)" 2018-11-02 12:09:12 +01:00
update.h Code Sanitization 2018-10-14 13:26:23 +02:00
vendor_array.h Code Sanitization 2018-10-14 13:26:23 +02:00
wifiscan.h Code Sanitization 2018-10-14 13:26:23 +02:00

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