What is Program Phases?
Program Phases is the next step after Hello World!
Example programs indexed using the Program Phases methodology employ the comparative analysis benefits of a Hello World! program while expanding the programs to include additional programming tasks. The indexed example programs found here illustrate the Program Phases methodology.
Each well defined main programming task is implemented in many different programming language/API combinations. Each of the programs that implement a particular main programming task is indexed according to the individual sub tasks defined by the main programming task. The indexing scheme that each program is indexed with allows the reader to easily cross reference programming sub tasks across different programming language/API implementations of the main programming task.
Definitions:
- Program Phases is a methodology for indexing computer programs called Program Phase Tasks.
- A Program Phase Task (main programming task) is a specially designed computer program that clearly illustrates specific functionality supported by an operating system, programming language, and application programming interface (API).
- Volume 1 of Program Phases, A Programming Language and API Translator describes four Program Phase Tasks:
- An implementation of a Program Phase Task is called a Program Phase and is assigned a unique number with respect to other Program Phases.
- Volume 1 of Program Phases, A Programming Language and API Translator, provides eighteen plus Program Phase implementations of each of the four Program Phase Tasks.
- Each Program Phase provides an indexed example program that illustrates how to implement a particular Program Phase Task using a given programming language/API combination on one or more platforms.
- The code in each Program Phase is organized (according to sub tasks) into sections called Code Blocks.
- Each Code Block is assigned a unique number called a Code Block Identifier (CBI).
- Each CBI takes the following form:
| <Program Phase ID>.<File Number*>.<Class Member/Function Number>.<Block Number> |
*Note that a class header file and its corresponding implementation file share a common file number even though they are two separate files.
| See Also |