A constructor is a special method that runs when an object is created, used to initialize its state into a valid starting condition. A destructor (or finalizer) runs when an object is destroyed, used to clean up resources.
{
String host;
{
(host == )
();
.host = host;
}
}
A good constructor ensures the object is never observable in an invalid state.
class FileWriter:
def __init__(self, path):
self.f = open(path, "w") # acquire resource
def close(self):
self.f.close() # explicit cleanup
def __enter__(self): return self
def __exit__(self, *a): self.close() # deterministic cleanup
with FileWriter("out.txt") as w: # closed automatically at block end
pass
| Language | Cleanup mechanism |
|---|---|
| C++ | Destructor ~T(), runs deterministically |
| Java/C# | GC + finalize/Dispose (non-deterministic; use try-with-resources / using) |
| Python | __del__ (unreliable timing); prefer context managers |
In garbage-collected languages, never rely on finalizers for releasing files, sockets, or locks — their timing is undefined. Use explicit close/Dispose/context managers.
Constructors are your guarantee that every object starts valid — the single best place to enforce required arguments and invariants.
Cleanup matters because finite resources (file handles, connections) leak if not released, and relying on GC for them causes intermittent, hard-to-debug exhaustion.