On 6/13/06, Adam <[EMAIL PROTECTED]> wrote:
Page 39 Listing 4.24 in the Phil's manual says differently... I wish what you said is correct - easier to manage. Please clarify. Thanks.
You're misinterpreting the text there. As Phil said in his answer, Listing 4.24 is an example of an optimisation where allowing async code to interrupt an atomic statement would have no detectable effects. But in cases where the effects would be detectable (i.e., if there is any shared state between the atomic statement and anything that interrupts it), such an optimisation would be illegal. It's all quite moot because we don't attempt to do such optimisations at this point. David Gay _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
