Eval considered

Using eval is almost always a bad idea. It's a crutch for bad designs, it opens giant security holes in your code, and in practice it's almost never needed to get actual stuff done.

>>12
Who givs a shit when these problems about FP are entirely contained within the program, where it's your imcompetence that is the failure, not FP nor ``life''? State and IO are not unsolved in FP.
Run through the C scenario in >>10 a few more times and you have a garbled mess of dog piss mascquerading as a program. Do it in Haskell or ML, where you change the signatures of functions A and B, and you have 10 minutes of satisfying the compiler followed by an equivalently clean program.