On 04/08/2015 16:34, Alexis King wrote:
And that, I think, is the problem: eval seems a lot like a “one size fits all” approach to problem solving. ... We write in high-level languages for a reason. There’s no reason to stunt their ability to abstract by directly calling eval.
I do understand that attitude of staying on top of a platform and in the "high levels" of a high level language. Exactly for those reasons some have written that pityful subroutine called "eval" and others even maintain it from time to time - just to not get your feets wet ;-) if not for a very good reason.
-- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
