2 ms·
Just because it has a name doesn’t make it a good idea necessarily. What one calls “initialization” someone else might call a “side effect”. In particular, so
by CoolGuySteve 8y ago
Just because it has a name doesn’t make it a good idea necessarily. What one calls “initialization” someone else might call a “side effect”.
In particular, sometimes you don’t want a bunch of allocations and locks firing on every function call and exit. C makes this behaviour explicit and C++ makes it implicit.