1 Revision history for Eval-Closure
6 - Remove a double layer of string eval that was introduced in 0.07 as an
7 intermediate step in figuring out the unique package thing - it's not
8 necessary with the final implementation, and just makes things slower
12 - the given source is now evaled in a unique package for every
13 eval_closure call (it used to always be evaled in the Eval::Closure
14 package, which was especially buggy). this is to avoid issues where one
15 eval_closure modifies the global environment (by, say, importing a
16 function), which could mess up a later call. unfortunately, this means
17 that the memoization stuff no longer works, since it will result in
18 memoized results using the original package, which defeats the purpose.
19 i'm open to suggestions on how to safely reenable it though.
21 - clean up a few stray lexicals we were still closing over in the eval
24 - The dumped source from setting $ENV{EVAL_CLOSURE_PRINT_SOURCE} didn't
25 show the captured variable creation properly. (Dave Rolsky)
28 - make sure Perl::Tidy doesn't look at @ARGV (rafl)
31 - stop using Memoize, it apparently doesn't work properly under mod_perl
32 in some situations (mateu)
35 - don't add #line directives when the debugger is active (alh)
38 - add terse_error option for throwing only the actual compilation error
40 - allow also specifying the line number for error reporting