Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
- Add one BUILD_DEPENDS to devel/p5-Devel-LexAlias for make test.
(upstream)
- Update to 0.13
--------------
0.13 2015-05-12
- one more fix for blead (eserte, jplesnik, #6)
Changes from previous:
----------------------
0.11 2013-07-30
- add "alias => 1" option for making closure variables actually alias the
closed over variables (so the variable referenced in the environment
hashref will actually be updated by changes made in the closure). (Toby
Inkster, #3)
0.10 2013-07-10
- fix pod links
0.09 2013-07-10
- support lexical subs on 5.18+
devel/p5-Eval-Closure from 0.06 to 0.08.
pkgsrc changes:
- change no-version dependency notation from x>=0 into x-[0-9]*
Upstream changes:
0.08 2012-02-09
- 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.
0.07 2012-02-03
- 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
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).
