Help with module name

Monks -

I have written a module I intend to release on CPAN which mimics the JavaScript functions setInterval() and clearInterval().

I have the "forks" version ready, and will also release a "threads" version.

My question is - what do you call this? "Interval" is already taken and means something else. "forks::interval" and "threads::interval" sound nice but I haven't contacted the forks/threads module maintainers yet.

Usage looks like this:

  use whatever::Interval;

  my $interval = whatever::Interval->setInterval(
    action   => \&do_stuff,
    interval => 1000, # One second
  );
  # "do_stuff()" gets executed once every second.

  # ...later...
  $interval->clearInterval();
[download]

Thoughts? Ideas? Does this functionality already exist in another module?

Comment on Help with module name Download Code

Replies are listed 'Best First'.
Re: Help with module name by ikegami (Patriarch) on Nov 20, 2006 at 18:03 UTC
Parallel:: might be of interest.	[reply]
Re: Help with module name by castaway (Parson) on Nov 21, 2006 at 08:09 UTC
I suggest you look for a name that closer describes what it does, instead of mimicing the javascript name. The purpose wasn't obvious to me at all until I read the comment in the example. Something like Schedule, or Repeat. There are a couple of these on CPAN, see Schedule::Cron for example. C.	[reply]
Re: Help with module name by alpha (Scribe) on Nov 21, 2006 at 07:51 UTC
Very nice.. Can't find any problems to solve with it though.. But still its' good	[reply]
Re: Help with module name by radiantmatrix (Parson) on Nov 22, 2006 at 18:12 UTC
How about "every"? `use Every ':threads'; my $process = Every->time( ms => 1000, call => \&do_stuff, args => [] +); $process->start(); #now do_stuff() will get called ever 1000 ms. # .. later... $process->stop();` [download] This would leave open the future possiblity of event- or condition-driven "Every" processes as well, instead of just `time`-driven. As for the `use` statement, you could either do a custom `import` sub (interface like above) or have `Every::threads`, `Every::fork` and so on. <–radiant.matrix–> Ramblings and references The Code that can be seen is not the true Code I haven't found a problem yet that can't be solved by a well-placed trebuchet	[reply] [d/l] [select]