<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I am not using packing to interface with C or to be compact.<div><br></div><div>My code is directly producing packets for some network protocol. No C in sight :). </div><div><br></div><div>And, as probably all those pesky :) network protocols around… Order of bytes and (expected) order of bits is - left to right.</div><div><br></div><div>I really do not understand why this is something hard to accept as standard (or at least cm3) way for bit packing?</div><div><br></div><div><div><div>On Jan 20, 2012, at 2:18 AM, Jay K wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: Tahoma; font-size: 13px; ">Anyway, if you just conserving space, then "BITS FOR" should work fine.<br>If you need to interface with C, and you can't change the C, you should be able to get something to work, but it will possibly be somewhat non-portable, esp. endian-specific.<br>I think besides endianness, there is another factor, where cm3 tries to be C-compatible.<br>Like, how aligned bitfields need to be.</span></span></blockquote></div><br></div></body></html>