We have to agree to disagree. Peace.
"A caller of a function in an imperative environment cannot assume anything about the scope of that function's access of mutable state within the program" This really doesn't make sense. main() { A a = new A(); f(); ...…
Yes. But do you understand that every one has its own partial, subjective view of that reality. Your post is your own view, not an neutral, scientific study. Your point ("mutable state equals additionnal arguments to…
Actually, my webapps are full of threads. Again, Imperative style is not the wrong way, and FP the right way. They are just different. Why not let people find their own way ? Just give the information they need to make…
All my methods take just a few argument, I learned to design carefully the state of my programs and manage adequatly how function access that state. Imperative programming works for me (and many others). You say I am…
We have to agree to disagree. Peace.
"A caller of a function in an imperative environment cannot assume anything about the scope of that function's access of mutable state within the program" This really doesn't make sense. main() { A a = new A(); f(); ...…
Yes. But do you understand that every one has its own partial, subjective view of that reality. Your post is your own view, not an neutral, scientific study. Your point ("mutable state equals additionnal arguments to…
Actually, my webapps are full of threads. Again, Imperative style is not the wrong way, and FP the right way. They are just different. Why not let people find their own way ? Just give the information they need to make…
All my methods take just a few argument, I learned to design carefully the state of my programs and manage adequatly how function access that state. Imperative programming works for me (and many others). You say I am…