AFAIK, functional programming is programming that doesn't modify state.
And, if all you're doing is taking material from real life and uploading into computers, then you're not modifying state at all.
AFAIK, functional programming is programming that doesn't modify state.
And, if all you're doing is taking material from real life and uploading into computers, then you're not modifying state at all.
Maybe I am misunderstanding what you wrote, but "state" in the context of functional programming refers to the state internal to the program, not the state external to the program. So whether the input data comes from the real world is orthogonal to the question of whether a program preserve state.
Interesting perspective. If I may ask, do you mind dropping 'root' privileges for a better chat / debate experience? That would probably help with your case.
FWIW I agree with that perspective and think it is a quite common one.
There are no authoritative definition AFAIK, but this is a way too coarse definition to qualify for me at least.
I think many equate FP with referential transparency, garbage collection, first class functions/closures. But usually it’s a sort of mix of all the above or opt-in. Standard ML makes it easy to mutate state for instance.
C is by no means a functional language. It is perhaps the definition of imperative; the poster child.
If I write my code primarily in a way that is simply supposed to achieve functionality then it's by definition functional programming.
Regardless of the language used!
[dead]
[dead]