Re: Time::RateLimit

[Jay Soffian]

 WRW == William R Ward William writes:

WRW [EMAIL PROTECTED] (Fglock) writes:
 Jay Soffian wrote:
calibrate();# takes a second or two to complete
 
 You could calibrate when installing the module, maybe.

WRW For years when calling rand() you had to remember to first call
WRW srand() to initialize the random-number generator.  Then a few
WRW versions of Perl ago, that requirement was removed - rand() will
WRW automatically initialize it if it has not already been done explicitly
WRW with srand().  You might do well to follow the example.

WRW Also calibrate is a pretty generic term that could easily conflict
WRW with a subroutine in the script that loads your module.
WRW calibrate_rate() might be less likely to cause problems.

Good points. Turns out I don't need the calibrate function at all
though, so I'll just remove it.

j.

Re: Date::Leapsecond

[Yitzchak Scott-Thoennes]

In article [EMAIL PROTECTED], fglock [EMAIL PROTECTED] wrote:
SYNOPSIS

  use Date::Leapsecond;
  use Time::Local;  

  $epoch_2000 = timegm(0,0,0,1,0,2000 - 1900);
  $epoch_1990 = timegm(0,0,0,1,0,1990 - 1900);
  print Seconds between years 1990 and 2000 are ;
  print Date::Leapsecond::ut1($epoch_2000) - 
Date::Leapsecond::ut1($epoch_1990); 
  print  instead of ;
  print $epoch_2000 - 
$epoch_1990; 

Looks good.  How do you handle the future?  Right now we only know the
actual leap seconds through 2002/12/30.  But you could make some kind of
prediction for dates beyond that.