Revision history for Eval-Closure
{{$NEXT}}
+ - Remove a double layer of string eval that was introduced in 0.07 as an
+ intermediate step in figuring out the unique package thing - it's not
+ necessary with the final implementation, and just makes things slower
+ and hides errors.
+
+0.07 2012-02-03
+ - the given source is now evaled in a unique package for every
+ eval_closure call (it used to always be evaled in the Eval::Closure
+ package, which was especially buggy). this is to avoid issues where one
+ eval_closure modifies the global environment (by, say, importing a
+ function), which could mess up a later call. unfortunately, this means
+ that the memoization stuff no longer works, since it will result in
+ memoized results using the original package, which defeats the purpose.
+ i'm open to suggestions on how to safely reenable it though.
+
+ - clean up a few stray lexicals we were still closing over in the eval
+
+0.06 2011-06-05
- The dumped source from setting $ENV{EVAL_CLOSURE_PRINT_SOURCE} didn't
show the captured variable creation properly. (Dave Rolsky)