Calling external support functions from other threads

[Dar Scott]

My second question...

On Jul 17, 2012, at 11:02 PM, Mark Wieder wrote:
> You may find some useful information in the notes to bug 1242.

From the second part of the first tip by Trevor:

> Usually I pass the following string through snprintf to SendCardMessage:
> 
> global gDispatchRevolutionMessage;try;send \"%s
> gDispatchRevolutionMessage\";catch errno;end try;put 0 into
> gDispatchRevolutionMessage
> 
> When using SendCardMessage in the context of an OS event I now use this string:
> 
> global gDispatchRevolutionMessage;try;send \"%s gDispatchRevolutionMessage\" to
> this card of this stack in 0 millisecs;catch errno;end try;put 0 into
> gDispatchRevolutionMessage


The use of try, presumably to catch errors in the send, is pretty clever.  I wonder if there is a chance for a name collision for errno.  Can errno clash with the context?

I am not able to infer the function of gDispatchRevolutionMessage.  What is that all about?

Dar