4 ms·
Compile time read have sense. Considering what we've known about the typical behavior of production programs for decades, why isn't there also an "Initializati
by stcredzero 10y ago
Compile time read have sense.
Considering what we've known about the typical behavior of production programs for decades, why isn't there also an "Initialization Time" in addition to Compile Time and "runtime." (Steady State Time?)
- steveklabnik 10y agoSome languages do have a "life before main", but it's not always clear that it's a good thing. I don't have a link offhand, but I think it has a bad rap because it's often used to initialize some kind of global state, with all the cons global state brings.
- ptman 10y agoPerl source filters
- stcredzero 10y agoI remember a study of production Python servers that showed that past an "initialization period" the types of objects in variables settled down and essentially became static. It seems to me that this is a very common across many languages, and that this pattern could be exploited in a number of ways. (Compiling "dynamic" languages in the above case.) I think it has a bad rap because it's often used to initialize some kind of global state, with all the cons global state brings. So then what if the language didn't have global state, or only had immutable global state?