Content deleted Content added
→Rewrite: Regarding paradigms |
→This sentence is not a reason: new section |
||
Line 142:
== Comparison with object-oriented programming ==
The table in the comparison with object-oriented programming section describes the difference in idioms between pure OO and pure procedural programming, not the difference in features, as both have functions, both have variables, and so forth. In OOP a message is information sent to a method, just as in PP, an argument is information sent to a function. Therefore the proper mate for "message" under the OO paradigm in this table is "argument." A "function call" is not information sent to a function, but rather the instantiation of the function itself, much as an object is not a class, but an instantiation of the class itself. <small>—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Max42|Max42]] ([[User talk:Max42|talk]] • [[Special:Contributions/Max42|contribs]]) 23:02, 6 June 2008 (UTC)</small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
== This sentence is not a reason ==
Comment about this sentence: "Procedural programming languages are also imperative languages, because they make explicit references to the state of the execution environment."
It might (perhaps) help someone like me reading this if "execution environment" were actually defined. It is used twice in this article (at the time of writing this) without being defined or explained.
How does making "explicit references to the state of the execution environment" make a language an imperative one? Earlier in the article, it is suggested that imperative langauages specify the steps the program must take to reach the desired state. That makes sense. Specifying what must happen chimes with the word "imperative". Making "references to the state of" something (something that isn't even defined) doesn't make sense as a reason, and is very abstract and confusing. Even if "execution environment" were clearly defined, the above sentence is most probably not an explanation why "Procedural programming languages are also imperative languages".
| |||