I like the name idea, but I'm skeptical of the interface suggestions. The code would lose readability and my module would be a lot more complex. In Memoize, you don't lose readability because a memoize'd sub still does the same stuff regardless of weather it's cached or not. In this application the behavior is different. I can see a code maintainer going nuts because this thing only sends an email every 5 minutes, no matter what he does and he doesn't know why until he sees that defer() call at the top.

If there's demand for it, though, I'd be happy to write it with both interfaces.

Can you think of a way to make it more compact without losing readability?

Anyone else have thoughts on that?

In reply to Re^2: RFC: Time Lock Module Idea? by pileofrogs
in thread RFC: Time Lock Module Idea? by pileofrogs

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.