Procedural programming: Difference between revisions

Content added Content deleted

Inline

Revision as of 15:38, 20 July 2008

Procedural programming describes a way of decomposing a programming problem, when a larger problem is decomposed into smaller ones by means of subprograms. This type of decomposition is called procedural. It is typical for imperative programming and functional programming paradigms.

In object-oriented programming procedural decomposition plays a subordinate role. Subprograms become methods of objects, which replace the former as building blocks.

Historically procedural programming played a decisive role in the transformation of engineering problems into programming solutions. Until recently the great majority of reusable software components has been designed, deployed, and maintained in the form libraries of subprograms.

@@ Line 1: / Line 1: @@
-[[Category:Encyclopedia]]'''Procedural programming''' describes a way of decomposition of a programming problem, when a larger problem is decomposed into smaller ones by means of subprograms. This type of decomposition is called ''procedural''. It is typical for [[imperative programming]] and functional programming paradigms.
+[[Category:Encyclopedia]][[Category:Programming Paradigms]]'''Procedural programming''' describes a way of decomposing a programming problem, when a larger problem is decomposed into smaller ones by means of subprograms. This type of decomposition is called ''procedural''. It is typical for [[imperative programming]] and functional programming paradigms.
 In [[object-oriented programming]] procedural decomposition plays a subordinate role. Subprograms become methods of objects, which replace the former as building blocks.
-Historically procedural programming played a decisive role in transformation of programming into engineering activity. Until present the great majority of reusable software components is designed, deployed, and maintained in the form libraries of subprograms.
+Historically procedural programming played a decisive role in the transformation of engineering problems into programming solutions. Until recently the great majority of reusable software components has been designed, deployed, and maintained in the form libraries of subprograms.