On Mon, Jan 12, 2009 at 11:17 AM, Michael Schippling <[email protected]>wrote:
> There "used to be" a pad/no-pad option especially for this. > Are the nx_ types defined to always be no-pad? I've looked at the code generated and the nx_types are defined as arrays of uint8_t. Not sure how the pad no_pad used to work. I suspect it is for multibyte objects such as uint16_t etc. But for the question originally asked int8_t were being asked about. eric > > thx > MS > > Eric Decker wrote: > >> >> >> On Mon, Jan 12, 2009 at 10:59 AM, Michael Schippling >> <[email protected]<mailto: >> [email protected]>> wrote: >> >> You could change datax to: nx_uint8_t datax[14] >> and then use a string or array copy to set it. >> You've only got 28 or 29 bytes (depending on the >> TOS version and standard settings) to play with >> in your message, and the other fields add up to >> 14 bytes already...or perhaps more if the int8's >> are padded -- in fact I would group those two >> int8's together in the hopes that the compiler >> will not pad them. >> >> >> The compiler won't pad them. if they are bytes. >> >> eric >> >> > -- Eric B. Decker Senior (over 50 :-) Researcher Autonomous Systems Lab Jack Baskin School of Engineering UCSC
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
