Methods that operate on state in C Sharp (C#) - Step-by-Step Execution

Concept Flow - Methods that operate on state

Create Object with Initial State

↓

Call Method on Object

↓

Method Accesses and Changes State

↓

State Updated

↓

Use Updated State

↓

End

This flow shows how a method is called on an object, accesses its internal state, changes it, and then the updated state is used.

Execution Sample

C Sharp (C#)

class Counter {
  private int count = 0;
  public void Increment() {
    count = count + 1;
  }
  public int GetCount() {
    return count;
  }
}

This code defines a Counter class with a count variable and methods to increase and get the count.

Execution Table

Step	Action	count Before	count After	Output
1	Create Counter object	N/A	0	N/A
2	Call Increment()	0	1	N/A
3	Call Increment()	1	2	N/A
4	Call GetCount()	2	2	2
5	End	2	2	N/A

💡 No more method calls; program ends with count = 2

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
count	N/A	0	1	2	2	2

Key Moments - 2 Insights

Why does the count variable change after calling Increment()?

Because Increment() method accesses the object's internal count variable and adds 1 to it, as shown in execution_table steps 2 and 3.

Does GetCount() change the count variable?

No, GetCount() only returns the current value of count without modifying it, as seen in step 4 where count before and after remain 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of count after the first Increment() call?

A 0

B 1

C 2

D N/A

💡 Hint

Check the 'count After' column at Step 2 in the execution_table.

At which step does the count variable stop changing?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'count Before' and 'count After' columns in steps 3 and 4.

If we call Increment() one more time after step 4, what would be the new count?

A 2

B 4

C 3

D 1

💡 Hint

Each Increment() adds 1 to count; after 2 increments count is 2, so one more makes it 3.

Concept Snapshot

Methods that operate on state:
- Methods can read and change an object's internal variables.
- Calling a method like Increment() updates the state.
- Methods like GetCount() can return state without changing it.
- State changes persist between method calls.
- Use methods to safely manage and update object data.

Full Transcript

This example shows a Counter class with a private variable count starting at 0. When we create a Counter object, count is 0. Calling Increment() adds 1 to count each time. Calling GetCount() returns the current count without changing it. The execution table traces each step: creation sets count to 0, first Increment changes count to 1, second Increment changes count to 2, then GetCount returns 2. The variable tracker shows count's value after each step. Key moments clarify that Increment changes state while GetCount does not. The quiz asks about count values at different steps and what happens if we call Increment again. This teaches how methods operate on and change an object's internal state in C#.

Practice

1. What is the main purpose of methods that operate on state in a C# class?

easy

A. To perform calculations without changing any data

B. To allow objects to keep and change their own data safely

C. To handle user input from the console

D. To create new classes from existing ones

Solution

1. Step 1: Understand what 'state' means in programming

   State refers to the data stored inside an object that can change over time.

2. Step 2: Identify the role of methods operating on state

   These methods allow the object to update or read its own data safely, keeping control inside the object.

3. Final Answer:

   To allow objects to keep and change their own data safely -> Option B

4. Quick Check:

   Methods on state = safe data change inside object [OK]

Hint: Think: methods change or read object's own data [OK]

Common Mistakes:

• Confusing methods on state with inheritance
• Thinking methods only perform calculations
• Believing methods handle external input only

2. Which of the following is the correct syntax for a method that changes an object's state in C#?

easy

A. public void UpdateName(string newName) { name = newName; }

B. void UpdateName(string newName) name = newName;

C. public UpdateName(string newName) { name = newName; }

D. public void UpdateName(string newName) => return name = newName;

Solution

1. Step 1: Check method declaration syntax

   In C#, methods must specify access modifier, return type, name, and parameters inside parentheses, with body in braces.

2. Step 2: Verify the method body updates the state correctly

   public void UpdateName(string newName) { name = newName; } correctly assigns newName to the field name inside braces.

3. Final Answer:

   public void UpdateName(string newName) { name = newName; } -> Option A

4. Quick Check:

   Correct method syntax = public void UpdateName(string newName) { name = newName; } [OK]

Hint: Remember method syntax: access + return type + name(params) { body } [OK]

Common Mistakes:

• Missing braces around method body
• Omitting return type
• Using return with void methods incorrectly

3. What will be the output of this C# code?

class Counter {
  private int count = 0;
  public void Increment() { count++; }
  public int GetCount() { return count; }
}

var c = new Counter();
c.Increment();
c.Increment();
Console.WriteLine(c.GetCount());

medium

A. 3

B. 1

C. 0

D. 2

Solution

1. Step 1: Trace the Increment method calls

   Each call to Increment increases count by 1. Two calls increase count from 0 to 2.

2. Step 2: Check the GetCount method output

   GetCount returns the current count, which is 2 after two increments.

3. Final Answer:

   2 -> Option D

4. Quick Check:

   2 increments = count 2 [OK]

Hint: Count increments twice, so output is 2 [OK]

Common Mistakes:

• Forgetting that count starts at 0
• Assuming Increment adds more than 1
• Confusing method names or outputs

4. Identify the error in this method that tries to update an object's state:

public void SetAge(int age) {
  int age = age;
}

medium

A. The method redeclares 'age' variable causing a conflict

B. The method is missing a return statement

C. The method should be static to update state

D. The method should not have parameters

Solution

1. Step 1: Analyze variable declarations inside the method

   The method declares a new local variable 'int age', which conflicts with the parameter 'age'.

2. Step 2: Understand how to update the object's field

   To update the object's state, assign the parameter to the field, e.g., this.age = age; without redeclaring.

3. Final Answer:

   The method redeclares 'age' variable causing a conflict -> Option A

4. Quick Check:

   Variable redeclaration error = The method redeclares 'age' variable causing a conflict [OK]

Hint: Don't redeclare parameter names inside method [OK]

Common Mistakes:

• Thinking missing return causes error in void method
• Assuming static needed to update instance state
• Believing parameters should be removed

5. You have a class BankAccount with a private field balance. You want to add a method Withdraw that subtracts an amount only if there is enough balance. Which method implementation correctly operates on the state safely?

hard

A. public decimal Withdraw(decimal amount) { return balance - amount; }

B. public void Withdraw(decimal amount) { balance -= amount; }

C. public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); }

D. public void Withdraw(decimal amount) { if (amount < 0) balance += amount; }

Solution

1. Step 1: Check for safe state update conditions

   Method should only subtract amount if balance is enough to avoid negative balance.

2. Step 2: Verify method behavior on insufficient funds

   public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); } checks amount <= balance and prints a message if not enough, preventing invalid state.

3. Final Answer:

   public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); } -> Option C

4. Quick Check:

   Safe state update with condition = public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); } [OK]

Hint: Check balance before subtracting to avoid negative state [OK]

Common Mistakes:

• Subtracting without checking balance
• Returning new value without updating state
• Adding amount when negative instead of subtracting