Safely and cleanly create closures via string eval

Edit Package perl-Eval-Closure
http://search.cpan.org/dist/Eval-Closure

String eval is often used for dynamic code generation. For instance,
'Moose' uses it heavily, to generate inlined versions of accessors and
constructors, which speeds code up at runtime by a significant amount.
String eval is not without its issues however - it's difficult to control
the scope it's used in (which determines which variables are in scope
inside the eval), and it can be quite slow, especially if doing a large
number of evals.

This module attempts to solve both of those problems. It provides an
'eval_closure' function, which evals a string in a clean environment, other
than a fixed list of specified variables. It also caches the result of the
eval, so that doing repeated evals of the same source, even with a
different environment, will be much faster (but note that the description
is part of the string to be evaled, so it must also be the same (or
non-existent) if caching is to work properly).

Refresh
Refresh
Source Files
Filename Size Changed
Eval-Closure-0.08.tar.gz 0000016746 16.4 KB
perl-Eval-Closure-old_Test-More.patch 0000003287 3.21 KB
perl-Eval-Closure.changes 0000002013 1.97 KB
perl-Eval-Closure.spec 0000002915 2.85 KB
Revision 10 (latest revision is 19)
Stephan Kulow's avatar Stephan Kulow (coolo) accepted request 122779 from Stephan Kulow's avatar Stephan Kulow (coolo) (revision 10)
- updated to 0.08
    - 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.
    - 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
Comments 0
openSUSE Build Service is sponsored by