---------- Forwarded message ---------- From: Raymond Wiker rwiker@gmail.com Date: Fri, Sep 24, 2010 at 2:51 PM Subject: Re: [pro] The Best Examples of "Code is Data" To: Kazimir Majorinc kazimir@chem.pmf.hr
I do not think that this is a case where eval is needed, and it is not a case where eval is likely to be either the best or the simplest solution.
Instead of using list-construction operations to construct a "function" to be eval'd, you can use the function-construction operator (lambda, that is). In addition to being more conventional (simply by not using eval), it also gives you a mechanism for passing parameters into your functions without resorting to specials. Two mechanisms, in fact - you can use ordinary parameters and closed-over variables.
On Thu, Sep 23, 2010 at 9:53 PM, Kazimir Majorinc kazimir@chem.pmf.hr wrote:
OK, but both of you paid more attention to the additional niceties or advantages, unspecified in the problem, than to confirm or reject the claim that eval is the best solution for problem under specified criteria "simpler is better."
It looks to me as implicit claim "Yes, eval is the best solution of that problem, but if the problem is developed further, other approaches (like few mentioned) will (soon?) prevail."
Is it right?