diff options
| author | EnricoGuccii <partyka.003@proton.me> | 2026-05-11 14:12:18 +0200 |
|---|---|---|
| committer | EnricoGuccii <partyka.003@proton.me> | 2026-05-11 14:12:18 +0200 |
| commit | a08cc07211cb0ffb569e54eff95825e2b5ebc861 (patch) | |
| tree | 980cfeaf7d142b5a06f632cb1ef75613ccd4127b /include | |
| parent | 35f5f33f83b8808bb9d3dc1b0c05536341ac1e36 (diff) | |
pio init
Diffstat (limited to 'include')
| -rw-r--r-- | include/README | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/include/README b/include/README new file mode 100644 index 0000000..49819c0 --- /dev/null +++ b/include/README @@ -0,0 +1,37 @@ + +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 convention is to give header files names that end with `.h'. + +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 |