On Sun, 2005-11-20 at 14:53 -0800, gabriele renzi wrote: > --- gabriele renzi <[EMAIL PROTECTED]> ha scritto:
> I agree I need to learn more C than I actually > understand, but if this was standard C when I'd be > calling SendMsg.send the stack would have not been > unwinded yet, so it would work just fine. > Instead send just queues the msg and so my msg is not > existing anymore, this is ok, but I don't understand > why sendDone seem to work just fine instead of > exploding in my face. That was the core question, I'm > sorry I failed to express it. > > Anyway, thanks for answering me. Well, from the radio stack's perspective, it was able to send the message just fine. It spooled out the bytes, calculated a CRC, etc. It doesn't check whether the contents of the message change, which is what happens when it's on the stack. Instead, the stack assumes it has exclusive access to the memory. Checking would be a race condition anyways, as there could always be changes between the check and the enqueue. Phil _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
