On Jan 30, 2013, at 12:23 PM, Michael Fogus wrote: >> RuntimeException EvalReader not allowed when *read-eval* is false. > > The problem is that the second eval gets (<the actual + function> 1 2 > 3) which invokes the right pathway triggering the exception. You can > trigger the same exception by: > > (binding [*read-eval* false] (eval (list + 1 2 3)))
Re-reading this, I'm clearly not grokking something here. Maybe I'm having a slow afternoon; send help. :-P This obviously ends up running through EvalReader — but why? How is LispReader ever involved at all? Thanks, - Chas -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
