diff options
| author | EnricoGuccii <partyka.003@proton.me> | 2025-12-23 16:59:20 +0100 |
|---|---|---|
| committer | EnricoGuccii <partyka.003@proton.me> | 2025-12-23 16:59:20 +0100 |
| commit | 4bd0a060d100c7fb9ad657c939b954b081b62016 (patch) | |
| tree | b6d1c4f7504c2c8fd5b561c5200447ad6a58501a /include/README | |
| parent | 967500ab8abefa6700941d589979176677ab0d72 (diff) | |
eee
Diffstat (limited to 'include/README')
| -rw-r--r-- | include/README | 37 |
1 files changed, 0 insertions, 37 deletions
diff --git a/include/README b/include/README deleted file mode 100644 index 630164d..0000000 --- a/include/README +++ /dev/null @@ -1,37 +0,0 @@ -
-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
|