changelog
[gitmo/Eval-Closure.git] / Changes
CommitLineData
bab69638 1Revision history for Eval-Closure
2
3{{$NEXT}}
24c2ec64 4 - Remove a double layer of string eval that was introduced in 0.07 as an
5 intermediate step in figuring out the unique package thing - it's not
6 necessary with the final implementation, and just makes things slower
7 and hides errors.
f1787475 8
90.07 2012-02-03
0de2a1d9 10 - the given source is now evaled in a unique package for every
11 eval_closure call (it used to always be evaled in the Eval::Closure
12 package, which was especially buggy). this is to avoid issues where one
13 eval_closure modifies the global environment (by, say, importing a
14 function), which could mess up a later call. unfortunately, this means
15 that the memoization stuff no longer works, since it will result in
16 memoized results using the original package, which defeats the purpose.
17 i'm open to suggestions on how to safely reenable it though.
18
19 - clean up a few stray lexicals we were still closing over in the eval
30d2281c 20
210.06 2011-06-05
5ba965a4 22 - The dumped source from setting $ENV{EVAL_CLOSURE_PRINT_SOURCE} didn't
23 show the captured variable creation properly. (Dave Rolsky)
cf37ba1a 24
250.05 2011-04-25
813ecda3 26 - make sure Perl::Tidy doesn't look at @ARGV (rafl)
db129fdc 27
280.04 2011-04-15
078e0056 29 - stop using Memoize, it apparently doesn't work properly under mod_perl
30 in some situations (mateu)
fafdf693 31
320.03 2011-03-02
7aa97030 33 - don't add #line directives when the debugger is active (alh)
1e39bf60 34
350.02 2011-01-26
0b16c8f6 36 - add terse_error option for throwing only the actual compilation error
37 (Shawn M Moore)
38 - allow also specifying the line number for error reporting
39 (Shawn M Moore)
a97d54fa 40
410.01 2010-11-14
bab69638 42 - Initial release