In my opinion, it means different things to different people. It is hard to make a definite statement to say that OOP does or doesn't belong to Imperative programming style.
Having said that, OOP is a way of managing state in an imperative program.
"It is hard to make a definite statement to say that OOP does or doesn't belong to Imperative programming style."
And yet you made one for some reason. :)
OOP is no more imperative than Functional is imperative. If you write impure functions you're not really being functional you're being imperative. If you write mutable objects full of procedures ("sequences of statements") you're not really being OO you're being imperative or procedural.
I'm not sure what was in your blood stream, but it doesn't sound like it was OO. ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello Fabricio,
In my opinion, it means different things to different people. It is hard to make a definite statement to say that OOP does or doesn't belong to Imperative programming style.
Having said that, OOP is a way of managing state in an imperative program.
Hi Naveen.
"It is hard to make a definite statement to say that OOP does or doesn't belong to Imperative programming style."
And yet you made one for some reason. :)
OOP is no more imperative than Functional is imperative. If you write impure functions you're not really being functional you're being imperative. If you write mutable objects full of procedures ("sequences of statements") you're not really being OO you're being imperative or procedural.
I'm not sure what was in your blood stream, but it doesn't sound like it was OO. ;)