changelog
[gitmo/Eval-Closure.git] / Changes
CommitLineData
bab69638 1Revision history for Eval-Closure
2
3{{$NEXT}}
fb4fd3f3 4
50.08 2012-02-09
24c2ec64 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
9 and hides errors.
f1787475 10
110.07 2012-02-03
0de2a1d9 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.
20
21 - clean up a few stray lexicals we were still closing over in the eval
30d2281c 22
230.06 2011-06-05
5ba965a4 24 - The dumped source from setting $ENV{EVAL_CLOSURE_PRINT_SOURCE} didn't
25 show the captured variable creation properly. (Dave Rolsky)
cf37ba1a 26
270.05 2011-04-25
813ecda3 28 - make sure Perl::Tidy doesn't look at @ARGV (rafl)
db129fdc 29
300.04 2011-04-15
078e0056 31 - stop using Memoize, it apparently doesn't work properly under mod_perl
32 in some situations (mateu)
fafdf693 33
340.03 2011-03-02
7aa97030 35 - don't add #line directives when the debugger is active (alh)
1e39bf60 36
370.02 2011-01-26
0b16c8f6 38 - add terse_error option for throwing only the actual compilation error
39 (Shawn M Moore)
40 - allow also specifying the line number for error reporting
41 (Shawn M Moore)
a97d54fa 42
430.01 2010-11-14
bab69638 44 - Initial release