Type checking rules in Compiler Design - Step-by-Step Execution

Concept Flow - Type checking rules

Start: Expression or Statement

↓

Identify Types of Operands

↓

Apply Type Rules

↓

Check Compatibility

↓

Type OK

↓

Proceed

The process starts by identifying operand types, applying rules to check compatibility, and either continuing if types match or reporting an error if they don't.

Execution Sample

Compiler Design

int a = 5;
float b = 3.2;
a = a + b;

This code tries to add an int and a float and assign the result to an int variable.

Analysis Table

Step	Expression	Operand Types	Type Rule Applied	Result	Action
1	int a = 5;	int literal	Assign int to int	OK	a set to 5
2	float b = 3.2;	float literal	Assign float to float	OK	b set to 3.2
3	a + b	int + float	Promote int to float, add floats	float	Result is float
4	a = a + b;	int = float	Assign float to int (possible loss)	Type Error	Error: cannot assign float to int without cast

💡 Type error at step 4 stops compilation due to incompatible assignment.

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
a	undefined	5 (int)	5 (int)	5 (int)	Error - no update
b	undefined	undefined	3.2 (float)	3.2 (float)	3.2 (float)

Key Insights - 2 Insights

Why can't we assign the result of 'a + b' directly to 'a'?

Because 'a + b' results in a float due to type promotion, but 'a' is an int. Assigning float to int without explicit conversion causes a type error (see execution_table step 4).

What happens to the int operand when adding int and float?

The int operand is promoted to float to match types before addition, ensuring the operation is valid (see execution_table step 3).

Visual Quiz - 3 Questions

Look at the execution table, what is the type of the expression 'a + b' at step 3?

A int

B float

C string

D error

💡 Hint

Check the 'Result' column in execution_table row for step 3.

At which step does the type checking process detect an error?

A Step 2

B Step 3

C Step 4

D No error detected

💡 Hint

Look at the 'Action' column in execution_table for the step where assignment fails.

If variable 'a' was declared as float instead of int, what would happen at step 4?

A No error, assignment is valid

B Type error remains

C Addition would fail

D Variable 'b' would cause error

💡 Hint

Refer to variable types and assignment compatibility in execution_table steps 3 and 4.

Concept Snapshot

Type checking rules verify that operations use compatible data types.
Operands are identified, and rules decide if types match or need promotion.
If types mismatch without conversion, a type error occurs.
Example: int + float promotes int to float before addition.
Assignments must match variable types or require explicit casts.

Full Transcript

Type checking rules in compiler design ensure that expressions and assignments use compatible data types. The process starts by identifying the types of operands in an expression. Then, type rules are applied to check if the operands can be combined or assigned without error. For example, when adding an int and a float, the int is promoted to float to perform the addition correctly. However, assigning a float result back to an int variable without an explicit cast causes a type error. This error stops compilation to prevent unexpected behavior. Understanding these rules helps avoid common mistakes like incompatible assignments or operations.

Practice

1. What is the main purpose of type checking rules in a compiler?

easy

A. To ensure that data types are used correctly in operations and assignments

B. To optimize the program's execution speed

C. To translate code into machine language

D. To manage memory allocation during runtime

Solution

1. Step 1: Understand the role of type checking

   Type checking rules verify that variables and expressions use compatible data types to avoid errors.

2. Step 2: Differentiate from other compiler tasks

   Optimization, translation, and memory management are separate compiler tasks, not type checking.

3. Final Answer:

   To ensure that data types are used correctly in operations and assignments -> Option A

4. Quick Check:

   Type checking = Correct data types [OK]

Hint: Type checking = matching data types in code [OK]

Common Mistakes:

• Confusing type checking with code optimization
• Thinking type checking manages memory
• Assuming type checking translates code

2. Which of the following is a correct type checking rule for assignment statements?

easy

A. Type checking only applies to function calls, not assignments

B. A variable can be assigned a value of any type without restrictions

C. Variables do not need to be declared before assignment

D. The type of the value assigned must match the variable's declared type

Solution

1. Step 1: Review assignment type rules

   In type checking, the value assigned must have the same type as the variable's declared type.

2. Step 2: Eliminate incorrect options

   Allowing any type or ignoring declarations violates type safety; type checking applies to assignments.

3. Final Answer:

   The type of the value assigned must match the variable's declared type -> Option D

4. Quick Check:

   Assignment types must match [OK]

Hint: Assignment value type = variable type [OK]

Common Mistakes:

• Ignoring variable declarations
• Assigning incompatible types
• Thinking type checking excludes assignments

3. Consider this code snippet:

int x = 5;
float y = 3.2;
x = y;

What will a strict type checker report?

medium

A. No error, assignment allowed

B. Warning but allowed at runtime

C. Type mismatch error: cannot assign float to int

D. Syntax error due to missing semicolon

Solution

1. Step 1: Identify variable types and assignment

   Variable x is int, y is float. Assignment tries to put a float into an int.

2. Step 2: Apply strict type checking rules

   Strict type checking disallows assigning a float value to an int variable without explicit conversion.

3. Final Answer:

   Type mismatch error: cannot assign float to int -> Option C

4. Quick Check:

   Float to int assignment = error [OK]

Hint: Assigning float to int causes type mismatch error [OK]

Common Mistakes:

• Assuming implicit conversion is automatic
• Confusing syntax errors with type errors
• Ignoring strict type checking rules

4. Identify the error in this code snippet under type checking rules:

string name = "Alice";
int age = "30";

medium

A. No error, both assignments are valid

B. Type error: assigning string literal to int variable

C. Syntax error: missing quotes around 30

D. Runtime error due to invalid conversion

Solution

1. Step 1: Analyze variable declarations and assignments

   name is a string assigned a string literal, which is correct. age is an int assigned a string literal "30".

2. Step 2: Apply type checking rules

   Assigning a string literal to an int variable violates type checking rules, causing a type error.

3. Final Answer:

   Type error: assigning string literal to int variable -> Option B

4. Quick Check:

   String to int assignment = type error [OK]

Hint: Assigning string to int causes type error [OK]

Common Mistakes:

• Thinking quotes around 30 are optional
• Confusing syntax errors with type errors
• Assuming implicit conversion from string to int

5. Given a function with parameters typed as int and float, which call violates type checking rules?

void process(int a, float b) { /*...*/ }

// Calls:
process(10, 5.5);
process(3.2, 4.1);
process(7, 2);

hard

A. process(3.2, 4.1);

B. process(10, 5.5);

C. process(7, 2);

D. All calls are valid

Solution

1. Step 1: Check parameter types for each call

   Function expects int then float. Call 1 passes int and float correctly. Call 2 passes float then float, which mismatches first parameter. Call 3 passes int and int, which may be allowed if int converts to float.

2. Step 2: Apply strict type checking

   Call 2 violates type checking because first argument is float but expected int. Call 3 is valid if implicit int to float conversion allowed for second parameter.

3. Final Answer:

   process(3.2, 4.1); -> Option A

4. Quick Check:

   First param must be int, call 2 fails [OK]

Hint: First argument must be int, float causes error [OK]

Common Mistakes:

• Assuming all numeric types are interchangeable
• Ignoring parameter order in function calls
• Thinking int cannot convert to float