Comparing old-style code with the latest-style code, one thing appears immediately: when all the methods processed a bunch of things at the same time (I mean, in particular, the Fortran code that I opened right now), current practice dictates that you have methods that do things, and methods that just call methods that do something.
What is this style formally called, and what was its trigger (examples: literature document, library / structure, only from self-consistent consensus)?
source
share