8 ms·
Because you can do functional programming in OOP. In the sense that it was originally intended, which is just writing pure functions to avoid side effects.
by throw1234651234 6y ago
Because you can do functional programming in OOP. In the sense that it was originally intended, which is just writing pure functions to avoid side effects.
- Insanity 6y agoKind of disagree - in theory you can, but everyone in your org needs to do so. You can't be a "a bit functional". And also depending on external libraries might be an issue. In practice most OOP code will violate some functional stuff.
- dddbbb 6y agoIntended according to whom?
- throw1234651234 6y agoThe definition: "It is a programming paradigm in which function definitions are trees of expressions that each return a value, rather than a sequence of imperative statements which change the state of the program" There is no reason you can't do this in C# or Java.