changelog
[gitmo/Eval-Closure.git] / Changes
CommitLineData
bab69638 1Revision history for Eval-Closure
2
3{{$NEXT}}
0de2a1d9 4 - the given source is now evaled in a unique package for every
5 eval_closure call (it used to always be evaled in the Eval::Closure
6 package, which was especially buggy). this is to avoid issues where one
7 eval_closure modifies the global environment (by, say, importing a
8 function), which could mess up a later call. unfortunately, this means
9 that the memoization stuff no longer works, since it will result in
10 memoized results using the original package, which defeats the purpose.
11 i'm open to suggestions on how to safely reenable it though.
12
13 - clean up a few stray lexicals we were still closing over in the eval
30d2281c 14
150.06 2011-06-05
5ba965a4 16 - The dumped source from setting $ENV{EVAL_CLOSURE_PRINT_SOURCE} didn't
17 show the captured variable creation properly. (Dave Rolsky)
cf37ba1a 18
190.05 2011-04-25
813ecda3 20 - make sure Perl::Tidy doesn't look at @ARGV (rafl)
db129fdc 21
220.04 2011-04-15
078e0056 23 - stop using Memoize, it apparently doesn't work properly under mod_perl
24 in some situations (mateu)
fafdf693 25
260.03 2011-03-02
7aa97030 27 - don't add #line directives when the debugger is active (alh)
1e39bf60 28
290.02 2011-01-26
0b16c8f6 30 - add terse_error option for throwing only the actual compilation error
31 (Shawn M Moore)
32 - allow also specifying the line number for error reporting
33 (Shawn M Moore)
a97d54fa 34
350.01 2010-11-14
bab69638 36 - Initial release