What to do if you don't want a default constructor? -- Sandor Dargo

Do we need a default constructor? What does it mean to have a default constructor? What happens if we donΓÇÖt have one? Those are the questions we are going after in this article.

What to do if you don't want a default constructor?

by Sandor Dargo

From the article:

A default constructor is a constructor that takes no arguments and initializes - hopefully - all the members with some default values. If you define no constructors at all, itΓÇÖll even be generated for you.

Do we need default constructors?

It really depends. LetΓÇÖs first approach this question from a design point of view. Does it make sense to represent an object where the members are default initialized?

If you represent a tachograph, it probably makes sense to have such a default state where all the counters are initialized to zero.

The tachograph is the device that records driving times and rest periods as well as periods of other work and availability taken by the driver of a heavy vehicle.

On the other hand, if you represent a person or a task identifier - which inspired me to write this article - it doesnΓÇÖt. A person with an empty name or a task ID with an empty ID doesnΓÇÖt make much sense.

Well, thatΓÇÖs the case from a design point of view. What about the technical aspects? What happens if we donΓÇÖt have a default constructor?

View the full article