[DGD] Maximum delay on call_outs?

Noah Gibbs noah_gibbs at yahoo.com
Thu Jul 19 22:03:51 CEST 2007


  Somebody else already answered this, suggesting making the function static. 
This will work, though certain hacks can make it annoying to do so.  You can
also, as you suggested, check the caller and make sure its a known/expected
object.

--- Rev Dr Ari D Jordon <x262sm102 at sneakemail.com> wrote:

> --Back in the dark ages (or at least on 7/19/2007 11:11 AM -0700), "Noah 
> Gibbs had the audacity to proclaim:
> 
> >   Are you making sure that no error is returned?  That seems like a more
> > likely problem than the amount of delay...
> 
> Well, call_out() is returning a positive value. However, reread the 
> call_out doc yet again and noticed a bit I'd missed before, about the 
> function not being private.  Whoops.  Changed that, and hopefully will work 
> now.  This does raise the question of how to prevent said function being 
> called by anything other than the call_out.  I'm guessing checking 
> this_object() against previous_object()?
> ---
> God was my copilot, but we crashed in the mountains and I had to eat him.
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd
> 





       
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow  



More information about the DGD mailing list