On Thu, 21 Jun 2001, Jason Hill wrote:
> This is an attempt to force components to interact through the narrow
> interface of commands and events. Finally, it allows us to modify the
It's useful to keep in mind that the tinyos programming "style" is much
different than C/C++. To me, it seems closer to a hardware description
language (e.g. verilog/vhdl) than C. At Rutgers we use interconnected
block diagrams to program in TOS.
Because it's compiled down to C, it's easy to break through the
TOS abstractions and fall into a C mentality. I've had to do this a couple
of times to keep strings in flash (side note: TOS could use a "read-only"
storage abstraction (frame) & stable R/W storage abstraction).
However, I think the TOS model is very clean; it just requires some
disciple to stick to in the current toolset.
-R
