[DGD] call_out delay

[Noah Gibbs]

  That's weird, and not normal specified behavior.  Has he checked to make
sure his system clock is reasonable?

  Normally a call_out happens after the specified integer number of
seconds, plus a small delay.  Usually, a very small delay.  There's more
in the mailing list archive about this.  Here's what I have on my web site
on the topic:

  From
"http://phantasmal.sourceforge.net/DGD/DGD_LPC_Ref.html#CalloutTiming":

If you start two callouts with a 5 second delay immediately after each
other, they could be executed in any order. However, they <will> both
be executed before a callout delayed for 6 seconds.

This is also the case for long-term (>= 128 seconds) and millisecond
callouts.


On Fri, 21 Feb 2003, Jay Shaffstall wrote:

> I'm using call_out with a delay to trigger events in my mud that need to 
> happen at specific intervals.  The call_out docs say, "If the delay is an 
> integer, the function will be called after approximately the specified 
> number of seconds".
> 
> How approximate is approximate?  On my Windows PC, things seem to work as 
> I'd expect.  One of my builders is using a Linux laptop, and has seen the 
> delays decrease until events are being fired continually (the actual value 
> being passed in for the delay hasn't changed).  However on his Linux PC, it 
> seems to work fine.
> 
> Has anyone else seen this sort of behavior, or have an idea as to the 
> probable cause?  If it's a problem likely to be isolated to his laptop, I'm 
> not too worried.

-- 
angelbob at monkeyspeak.com
See my page of DGD documentation at
"http://phantasmal.sourceforge.net/DGD/"
If you post to the DGD list, you may see yourself there!


_________________________________________________________________
List config page:  http://list.imaginary.com/mailman/listinfo/dgd