[Tinyos Core WG] TOSThreads TEP

Vlado Handziski handzisk at tkn.tu-berlin.de
Tue May 20 16:26:55 PDT 2008


On Wed, May 21, 2008 at 1:13 AM, Philip Levis <pal at cs.stanford.edu> wrote:

>
> On May 20, 2008, at 4:09 PM, Vlado Handziski wrote:
>
>>
>> I am not concerned about the binary code only. Leaving out code with
>> #ifdefs is not what I consider "completely optional". Apart from being ugly,
>> just having the threading code in the default components is enough to
>> completely confuse the users about what TinyOS really is and how they should
>> develop their applications.
>>
>
> There's always been a tension between #ifdef and component shadowing, and
> there's a tradeoff. I mean, the interrupt handler could call a C function,
> which is defined one way for each approach (null or epilogue).
>
>
You don't get my point. I don't want to remember to always call a C function
at the end of my handlers, dummy or not. I want my old event-driven OS :)

Vlado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-2.0wg/attachments/20080521/f29d8fef/attachment.htm 


More information about the Tinyos-2.0wg mailing list