subrata, a simple application could be handled as follows:
- Split your source code into the desired files. DO NOT include function and variable definitions in the source files
- Create a global include file with all function definitions. #include this file into all your source files
- Place global variable definitions into the global include file: these will be available to all functions in the program, whichever is the source code functions are in
- The same with macros and other useful elements you need
A similar but more structured approach can be found taking as an example iconedit application shipped with CVI ( <cvidir>/samples/apps/iconedit folder 😞 here every source file has an associated header file with functions and variable definitions for elements common to more than one module; these files are included in every source file that needs them; elements confined to a single source file are defined at this level.
Such an approach in my opinion, while it is correct for large, modular and heavily structured applications, is oversized for little ones and can be difficult to understand and maintain (i.e. the cost of this structure is not justified by the application type). But this evaluation is heavily dependent on personal and company standards.
