What is procedural programming and not procedural programming?

Asked

Viewed 6,201 times

10

Li in that reply, but without many details, that:

"[...] procedural programming is an evolution of programming structured [...]"

And in this answer also:

[...] procedural programming is something that, to some extent, inevitable [...]

And on Wikipedia says that:

[...] sometimes used as a synonym for imperative programming [...]

But what really is procedural programming and not procedural programming?

  • That and indeed a doubt of mine, is not a criticism, I see several questions of this kind that learn to be made only to receive points. if it is to bring content, there is no way to even answer your question?

  • 1

    There’s nothing wrong with that @Jhonatandevss to answer your question: http://answall.com/help/self-answer

  • @Jhonatandevss The system allows you to answer your question yourself, there is even an option for this when you are creating a question. Generally, what people do is just bring content to the site, and make it more complete. I can’t tell if that’s his case, but it happens quite often. If you have any questions about this type of thing or other related to the site, you can use the Meta to and ask about the site. There times users and moderators answering this kind of question, which is normal.

1 answer

7


Basically it is the programming that structures the execution through watertight routines that are called as needed. Normally we call them functions, but it doesn’t have to be exactly that way.

Usually these routines have parameters to communicate with other parts of the code and may return some value, but it is not required, although getting confused mix all or little powerful not allow any communication.

Certainly the definition of this is not "a programming based on procedures (procedures)". Well, it is, but you have to be careful because the procedure is a routine watertight mechanism. One that is little used in most modern languages explicitly. Of course a function that returns nothing (in general void) is still a procedure. The term procedural is used as generic form.

Just as functional programming is not "the one that has functions", because if it were the case almost every language would be functional.

The procedural paradigm is secondary and refers more to the organization of the code as a whole, as well as to object orientation.

The main thing that differs from the object-oriented procedural is that the former glorifies the procedures, the behavior, and the latter glorifies the object, the state (curiously hiding them).

[...] procedural programming is an evolution of structured programming [...]

Structured programming is concerned only with the flow of code and not its compartmentalization.

[...] procedural programming is something that, to some extent, is inevitable [...]

I do not agree that the use of procedural is inevitable. The imperative is almost inevitable. I say this in What is a paradigm?.

[...] sometimes used as a synonym for imperative programming [...]

It is used erroneously as a synonym for imperative.

  • 3

    an example with code ?

Browser other questions tagged

You are not signed in. Login or sign up in order to post.