eval stinks in such an application

Admittedly, it at least smells funny. However, I personally don't like to tell people in those situations that it is unacceptable in an absolute sense, because we don't know what's their application is, and what risk they are willing to take (in exchange for easier programming). That's why I outlined every risk I was aware off. With other words: Instead of saying: "Don't shoot yourself in the head", I prefer saying: "You can shoot yourself in the head, but be aware that there will be a hole afterwards". ;-)

Having said this, I must admit that I would use such an eval solution for work I only use myself (not paid work for the customer), knowing well that I can't blame anyone but myself if I get bitten....