4 ms·
Boy is that ever the case! The lengths people will discuss spacing after method declarations, while being completely ignorant of the architectural issues that
by mpweiher 8y ago
Boy is that ever the case! The lengths people will discuss spacing after method declarations, while being completely ignorant of the architectural issues that are rotting their code-base.
> comfort zone
Tentative essay title: Can Programmers be Liberated from the Gentle Tyranny of Call/Return?
> actually morphing your language
Yes. And no. First let's have a look at what "morphing the language" means, by way of natural language. When we use natural languages, we can mostly adequately describe anything we want to using the mechanisms available. Sometimes, we need a new vocabulary, sometimes a set of interlocking vocabulary, i.e. jargon. I haven't really seen a case where we need to tinker with the structure of the language, with the grammar.
When we add a function, set of functions, interlocking objects/methods etc. I would say that we are also adding vocabulary. And that should be sufficient. The fact that it is not sufficient to me suggests that our fundamental "grammar" (not grammar of the surface syntax) is insufficient, not that we need to be able to make up grammar on the spot every time.
Of course making up grammar on the spot also solves the original problem, but it does lead to all these follow-on problems. One being that making up grammar on-the-spot is much more complex than just adding vocabulary, and so you are likely to get it horribly wrong. The other being comprehensibility.