Why do we need a private constructor?

Suppose we’re designing a special type of car, SuperCar. We want to ensure that every SuperCar that rolls out from the factory is top-notch, with all the advanced features and safety measures properly implemented. But we don’t want just anyone to be able to build a SuperCar without following the right procedures or meeting certain standards.

So, what should we do? We keep the blueprints and assembly instructions for the SuperCar inside the factory, and only trained engineers and technicians can access them. This way, we ensure that every SuperCar is built according to our high standards and specifications.

In programming, a private constructor is like those restricted blueprints and assembly instructions inside the car factory. It’s a special method inside the SuperCar class hidden from the outside world. This private constructor controls how new SuperCar objects are created, ensuring they’re built correctly and meet all the required standards.

Here’s how we can relate this to the concept of a private constructor:

• Controlled construction: Just like only trained engineers in the car factory can access the blueprints and build a SuperCar, a private constructor controls how new SuperCar objects are constructed. It ensures that only the right methods or conditions can create new SuperCar instances.

• Prevent unauthorized creation: By hiding the constructor, we prevent anyone from creating SuperCar objects without following the proper procedures or meeting certain requirements. This helps maintain the integrity and quality of the SuperCar class.

• Encapsulation of design: Keeping the constructor private encapsulates the construction logic inside the SuperCar class. This means the details of how a SuperCar is constructed are hidden from the outside world, making the class easier to manage and maintain.

Coding example

Let’s write down a complete code on the scenario above:

Code explanation

• Lines 4–8: The SuperCar class represents a special type of car. It has private member variables model, year, and assembled.

• Line 11: The SuperCar class has a private constructor, which means that objects of this class cannot be created directly using the new keyword. Instead, the create static method is used to create new SuperCar objects.

• Lines 15–22: The create() static method is used to create a new SuperCar object. It checks if the provided model is not empty and the year is greater than 0 before creating the object. If the conditions are not met, it returns nullptr, indicating that the object creation failed.

• Lines 25–32: The assemble() method is used to mark the car as assembled. It checks if the car has already been assembled before marking it as assembled.

• Lines 35–40: The displayDetails() method is used to display the details of the SuperCar, including the model, year, and whether it has been assembled or not.

• Lines 45–54: In the main() function, an attempt is made to create a SuperCar object using the create() method. The car details are displayed before and after assembling the car. An attempt to create another SuperCar object directly using the new keyword would result in a compilation error due to the private constructor.