Next | Query returned 27 messages, browsing 21 to 30 | previous

History of commit frequency

CVS Commit History:


   2014-05-14 04:15:24 by Hiramatsu Yoshifumi | Files touched by this commit (2) | Package updated
Log message:
Update devel/p5-Eval-Closure to 0.11.

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+
   2013-05-31 14:42:58 by Thomas Klausner | Files touched by this commit (2880)
Log message:
Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.
   2012-10-31 12:19:55 by Aleksej Saushev | Files touched by this commit (1460)
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
   2012-10-03 23:59:10 by Thomas Klausner | Files touched by this commit (2798)
Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
   2012-03-22 14:27:21 by Jens Rehsack | Files touched by this commit (2)
Log message:
Updating package for Perl5 module Eval::Closure from CPAN in
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
   2011-08-23 10:53:08 by David Brownlee | Files touched by this commit (1)
Log message:
Tune down requirements
   2011-08-23 10:50:14 by David Brownlee | Files touched by this commit (4) | Imported package
Log message:
Added devel/p5-Eval-Closure version 0.06

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).


Next | Query returned 27 messages, browsing 21 to 30 | previous