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.
And, if all you're doing is taking material from real life and uploading into computers, then you're not modifying state at all.
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.
Regardless of the language used!
> C in indeed a functional language […]
… which it isn’t, it’s imperative ¯\_(ツ)_/¯
Probably depends on at what level you see things. If you visit and probably live in Japan, then you develop the concept of 'cryptocurrency'. You then subsequently develop intellectual property around the 'concept' of 'cryptocurrency'.
Is this really 'imperative' programming? I'd say not but depending on at what level you see things, then it could be.
At project level, then it's purely functional.
Calling C a functional language because you’re able to manually emulate one feature that functional languages give you automatically, is like claiming C is a garbage collected language because ‘at the project level’ you remember to call free().
I can’t follow or understand your japan/crypto analogy, I’m sorry.