---
- branch: MAIN
  date: Tue Aug 23 08:50:14 UTC 2011
  files:
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-Eval-Closure/Makefile
    pathrev: pkgsrc/devel/p5-Eval-Closure/Makefile@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-Eval-Closure/DESCR
    pathrev: pkgsrc/devel/p5-Eval-Closure/DESCR@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-Eval-Closure/buildlink3.mk
    pathrev: pkgsrc/devel/p5-Eval-Closure/buildlink3.mk@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-Eval-Closure/distinfo
    pathrev: pkgsrc/devel/p5-Eval-Closure/distinfo@1.1.1.1
    type: imported
  id: 20110823T085014Z.215325086461c6064a2491598981c763103b479f
  log: "Added devel/p5-Eval-Closure version 0.06\n\nString eval is often used for
    dynamic code generation. For instance,\nMoose uses it heavily, to generate inlined
    versions of accessors\nand constructors, which speeds code up at runtime by a
    significant\namount. String eval is not without its issues however - it's\ndifficult
    to control the scope it's used in (which determines which\nvariables are in scope
    inside the eval), and it can be quite slow,\nespecially if doing a large number
    of evals.\n\nThis module attempts to solve both of those problems. It provides\nan
    eval_closure function, which evals a string in a clean environment,\nother than
    a fixed list of specified variables. It also caches the\nresult of the eval, so
    that doing repeated evals of the same source,\neven with a different environment,
    will be much faster (but note\nthat the description is part of the string to be
    evaled, so it must\nalso be the same (or non-existent) if caching is to work properly).\n\nStatus:\n\nVendor
    Tag:\tTNF\nRelease Tags:\tpkgsrc-base\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/p5-Eval-Closure'
  unixtime: '1314089414'
  user: abs