Hi,

The keyword "async" is used to notify the nesC compiler that the event is 
executed as a part of an intterupt handler. This allows nesC to generate 
warnings of race-condition. For example, if you have used a global 
variable in an async event and variable has also 
been used somewhere else in your program (but not in the atomic section) 
then you should see a warning of 
potential race-condition on compilation. Please note that atomic 
sections disable the intterupts.

Regards,
Manjunath D

################################################################################################################
***************************************************************************************************************

On Mon, 28 Dec 2009, Qiyuan Zhang wrote:

> Spam detection software, running on the system 
> "mail.Millennium.Berkeley.EDU", has
> identified this incoming email as possible spam.  The original message
> has been attached to this so you can view it (if it isn't spam) or label
> similar future email.  If you have any questions, see
> the administrator of that system for details.
>
> Content preview:  Hi, everyone. I just began learning TinyOS. I have some 
> problems
>   concerning sync and async command/event handlers. What's the exact meaning
>   of these two keywords? If a command is of sync which means it can only be
>   called in a synchronous context, does that mean it can be preempted by an
>   async command? If the command is of async, is it that two async commands
>  can preempt each other? Is it right to use atomic in a sync command? [...]
>
>
> Content analysis details:   (4.0 points, 3.3 required)
>
> pts rule name              description
> ---- ---------------------- --------------------------------------------------
> 1.5 FROM_STARTS_WITH_NUMS  From: starts with many numbers
> 0.0 HTML_MESSAGE           BODY: HTML included in message
> -0.7 BAYES_20               BODY: Bayesian spam probability is 5 to 20%
>                            [score: 0.1264]
> 1.8 MIME_BASE64_TEXT       RAW: Message text disguised using base64 encoding
> 1.5 FROM_EXCESS_BASE64     From: base64 encoded unnecessarily
>
> The original message was not completely plain text, and may be unsafe to
> open with some email clients; in particular, it may contain a virus,
> or confirm that your address can receive spam.  If you wish to view
> it, it may be safer to save it to a file and open it with an editor.
>
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to