Access specifiers in C++ - Time & Space Complexity

Time Complexity: Access specifiers

O(1)

Understanding Time Complexity

Access specifiers control who can use parts of a program, like private or public sections in a class.

Access specifiers are checked at compile-time and do not affect runtime performance. Let's analyze this code's time complexity.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Box {
private:
    int secret;
public:
    int openBox() {
        return secret;
    }
};

int main() {
    Box b;
    int value = b.openBox();
    return 0;
}
    

This code defines a class with private data and a public method to access it.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Accessing a private variable through a public method.
• How many times: Happens once in this example, no loops or recursion.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	1 simple access
100	1 simple access
1000	1 simple access

Pattern observation: Execution is constant time; access specifiers add no significant runtime overhead. Operations do not grow with input size.

Final Time Complexity

Time Complexity: O(1)

This means the time is constant regardless of input size, since there's only one constant-time access.

Common Mistake

[X] Wrong: "Accessing private data is slow because of extra checks."

[OK] Correct: Access checks happen at compile time or very fast at runtime, so they don't slow down the program noticeably.

Interview Connect

Understanding how access specifiers affect performance helps you write clear and efficient code, a skill valued in real projects.

Self-Check

"What if we accessed private data directly without a method? How would the time complexity change?"

Practice

1. Which access specifier allows members of a class to be accessed from anywhere in the program?

easy

A. protected

B. private

C. public

D. internal

Solution

1. Step 1: Understand access specifiers

   Public members are accessible from any part of the program, unlike private or protected.

2. Step 2: Compare with other specifiers

   Private restricts access to inside the class only; protected allows access in derived classes.

3. Final Answer:

   public -> Option C

4. Quick Check:

   Access anywhere = public [OK]

Hint: Public means accessible everywhere, private means hidden [OK]

Common Mistakes:

• Confusing private with public
• Thinking protected is accessible everywhere
• Assuming internal is a C++ specifier

2. Which of the following is the correct way to declare a private member variable int age inside a class?

easy

A. private int age;

B. private:
int age;

C. int age private;

D. int private age;

Solution

1. Step 1: Recall C++ syntax for access specifiers

   Access specifiers are labels followed by a colon, then members are declared below.

2. Step 2: Identify correct syntax

   private: int age; uses 'private:' followed by 'int age;' which is correct syntax.

3. Final Answer:

   private: int age; -> Option B

4. Quick Check:

   Access specifier label + colon = correct [OK]

Hint: Access specifiers end with colon, members declared below [OK]

Common Mistakes:

• Placing access specifier before type
• Missing colon after access specifier
• Trying to put access specifier after variable

3. What will be the output of this code?

class Test {
private:
    int x = 5;
public:
    int getX() { return x; }
};

int main() {
    Test t;
    // std::cout << t.x << std::endl; // Line A
    std::cout << t.getX() << std::endl;
    return 0;
}

medium

A. 5

B. Compilation error at Line A

C. 0

D. Runtime error

Solution

1. Step 1: Understand private member access

   The variable x is private, so direct access like t.x is not allowed (Line A is commented out).

2. Step 2: Use public getter method

   The method getX() is public and returns x's value, so std::cout << t.getX() prints 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Private hidden, public getter shows 5 [OK]

Hint: Private members need public methods to access outside [OK]

Common Mistakes:

• Trying to access private variable directly
• Expecting 0 as default value
• Confusing compilation and runtime errors

4. Identify the error in this code snippet:

class Base {
protected:
    int value = 10;
};

class Derived : public Base {
public:
    void show() {
        std::cout << value << std::endl;
    }
};

int main() {
    Derived d;
    d.show();
    std::cout << d.value << std::endl;
    return 0;
}

medium

A. Error: Cannot access protected member 'value' from main using object

B. Error: Cannot access protected member 'value' inside Derived class

C. Error: Missing semicolon after class Derived

D. No error, code runs and prints 10 twice

Solution

1. Step 1: Check access to protected member inside Derived

   Derived class can access protected members of Base, so d.show() works and prints 10.

2. Step 2: Check access to protected member from main

   Main function cannot access protected members directly via object, so std::cout << d.value causes compilation error.

3. Final Answer:

   Error: Cannot access protected member 'value' from main using object -> Option A

4. Quick Check:

   Protected accessible in subclass, not outside [OK]

Hint: Protected members hidden outside class and subclasses [OK]

Common Mistakes:

• Thinking protected is public
• Assuming main can access protected members
• Missing error on direct access in main

5. You want to design a class where some data is hidden from everyone except derived classes, and some functions are accessible everywhere. Which access specifiers should you use for data and functions respectively?

hard

A. Data: private, Functions: public

B. Data: protected, Functions: private

C. Data: public, Functions: protected

D. Data: protected, Functions: public

Solution

1. Step 1: Determine data access for derived classes only

   Protected data is hidden from outside but accessible in derived classes, fitting the requirement.

2. Step 2: Determine function access for everyone

   Functions accessible everywhere must be public.

3. Final Answer:

   Data: protected, Functions: public -> Option D

4. Quick Check:

   Protected data + public functions = correct design [OK]

Hint: Protected hides data, public shares functions [OK]

Common Mistakes:

• Using private data blocks derived classes
• Making functions private hides them outside
• Confusing public and protected roles