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.

>>15
No, also global state is good which I've found out in practice. Threading stuff through function arguments is painful. What we need to help debugging is protected globals to restrict in which functions a global may be modified.

The functional way of "mutable globals are evil!!1" is like curing headache with an axe.