Modular Programming

In single-chip microcomputer application systems, especially for large and complex systems, it is not feasible to put them in one file because there are so many sensors and processing modules. At this time, modular processing is required.

Make each module into a .c file and a .h file. Functions in a .c file will only call each other, and will not call functions in other files. Try to minimize cross-calling of functions in different files. Here are a few issues to pay attention to:

(1) Measures to prevent duplicate inclusion of module header files

At the beginning of the .h file in each module, to prevent repeated inclusion, use the following code:

#ifndefine xxx //If xxx is not defined, compile the following statement

#define xxx //Then define xxx so that it is included only once. The next time you check, you will find that it has been defined.

……. // If xxx is included, it will not be included again

#endif

(2) Code encapsulation

1. The function is declared in the header file and the function body is placed in the .c file;

2. Macro definitions that are only called in this .c file should be placed in the .c file, and macro definitions that need to be called by other files should be placed in the header file;

3. Use global variables as little as possible. When you must use them, put them in the .c file for your own use. When the global variable needs to be called externally, declare it with extern in the .h file.