Conversely, I don't consider it very likely that different applications would put their own messages under SurgeMsg, so perhaps SurgeMsg is not really a container msg and thus does not even need its own type at all.
I sort of meant that there are different kind of Surge messages; sensor data messages, route data messages, etc.
As a sidenote, getBuffer() doesn't seem to do anything that couldn't be done at compile time. All it does is make a call to offsetof() to find the start of the data field, and I'd imagine that's a compile-time macro anyway.
Absolutely. But it requires a bit of language/compiler support to fold the constants. The idea was basically, "How can we get the behavior we want, without doing a lot of work on what might be the wrong thing, or introducing compilation complexities?" That is, just use C. It's not the right long-term solution.
Phil
-------
"We shall not cease from exploration And the end of all our exploring Will be to arrive where we started And know the place for the first time."
- T. S. Eliot, 'Little Gidding'
_______________________________________________ Tinyos-users mailing list [EMAIL PROTECTED] http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users
