C++ Programming: Introduction to Program Development Study Guide

Learning Objectives for C++ Program Development

The following objectives outline the core competencies to be acquired in this chapter regarding C++ programming:

• Program Components: Become familiar with basic components, including functions, special symbols, and identifiers.
• Data Types: Explore simple data types and the specific properties of the string data type.
• Arithmetic Operators: Discover how to utilize and implement logical arithmetic operators.
• Expression Evaluation: Examine the processes by which a program evaluates complex arithmetic expressions.
• Assignment Statements: Learn the definition, syntax, and functional purpose of assignment statements.
• Data Input: Discover the methodologies for inputting data into computer memory using input statements.
• Increment and Decrement: Become familiar with the syntax and application of increment and decrement operators.
• Output Results: Examine various ways to output computational results using output statements.
• Preprocessor Directives: Learn the usage and necessity of preprocessor directives in the C++ environment.
• Program Structure: Explore the proper structural organization of a program, including the effective use of comments.
• Writing Programs: Acquire the fundamental skills necessary to write a complete C++ program.

Basic Structure of a C++ Program

A standard C++ program follows a specific hierarchical structure:

• Preprocessor Directive: #include <iostream>
• Namespace Declaration: using namespace std;
• Main Function Header: int main()
• Function Body: Enclosed in braces { } containing:
  • Declaration statements
  • Executable statements

Example Program Structure (Addition):

#include <iostream>
using namespace std;

int main(void) {
    int x, y, total;
    x = 10;
    y = 20;
    total = x + y;
    cout << "Total:" << total;
    return 0;
}

Preprocessor Directives and Header Files

C++ utilizes a collection of library files that contain pre-written code for common tasks.

• Header Files: Every library file has a unique name and is referred to as a "header file."
• Syntax for Inclusion: #include <header file name>
• The #include Directive:
  • Usually placed at the very top of the program.
  • Function: Inserts the literal contents of the specified header file into the program.
  • Example: #include <iostream> makes input/output functions like cin and cout available for use.
  • Critical Constraint: Never place a semicolon $;$ at the end of an #include line.

Namespaces and Scope

To manage identifiers and avoid naming conflicts, C++ uses namespaces.

• Namespace std: cin and cout are declared within the iostream header, but they reside within a specific declarative region called namespace std (standard).
• Usage: To use these standard functions easily, the statement using namespace std; provides a scope that allows the program to recognize them.

The Use of Comments in C++

Comments are essential for documenting code to help readers understand the logic. There are two primary types:

• Block Comments: Used for multi-line documentation. Enclosed between /* and */ tokens.
  • Example Style 1:cpp /* This is a block comment that covers two lines. */         
  • Example Style 2 (Common standard): Placing opening and closing tokens on their own lines, sometimes with asterisks at the start of each line to mark the comment clearly.
• Line Comments: Used for single-line notes. Begins with // and terminates at the end of the line.
  • Full line example: // This is a whole line comment.
  • Partial line example: a = 5; // This is a partial line comment.

Identifiers: Naming Program Elements

An identifier is a name defined by the programmer for elements such as variables and functions.

• Rules for Valid Identifiers:

  • Must consist only of alphabets, digits, or underscores _.
  • The first character must be an alphabet or an underscore.
  • Identifiers cannot be identical to C++ keywords or reserved words.

• C++ Keywords: These are reserved words with predefined meanings and must be written in lowercase. They cannot be repurposed as identifiers.

Valid vs. Invalid Identifiers Table: