Suggestion: the callingHandler

[Scott Raney]

On Sat, 31 May 2003 curry <curry at pair.com> wrote:

> How about a function that returns the name of the handler that called 
> the current handler? For example, this would be useful when a handler 
> needs to reset each time a different handler calls it, or to keep 
> track of different sets of data for each handler that calls it.

You can get this information with the executionContexts function.  I
hesitate to even mention it, however, because it was designed for
debugging purposes *only*: using it for conditional execution would
be, IMHO, heinous.  Use an optional parameter instead unless you want
your status as an xTalk wizard permanently revoked.
  Regards,
    Scott

> Curry

********************************************************
Scott Raney  raney at metacard.com  http://www.metacard.com
MetaCard: You know, there's an easier way to do that...