http://www.perlmonks.org?node_id=1019545


in reply to Re^3: Managing capture
in thread Managing capture

> when doing reviews you should be checking for cycles, esp with anonymous subs

I agree with this very much. But I think it is a hard problem. The intention of this pragma would be to make cycles caused via capture easier to spot in code review.

Replies are listed 'Best First'.
Re^5: Managing capture
by Anonymous Monk on Feb 19, 2013 at 13:19 UTC

    I agree with this very much. But I think it is a hard problem. The intention of this pragma would be to make cycles caused via capture easier to spot in code review.

    Its not really that hard :) Devel::Cycle - Find memory cycles in objects

    It is easy to modify perlcritic ProhibitConditionalDeclarations to alert yo to closures for a code , and then you can further investigate to decide if they're really trouble, or ok