[Click] CLICK_BYTE_ORDER

[Koen Beel]

Thanks Beyers and Jason!

So I should use uintX_t variables when the number of bits are
important (e.g. defining the structure of a header).
But for other use (e.g. a counter in a for loop) I can just use int.

And atomic? When do you have 'synchronization'? e.g. in
elements/ip/checkipheader.hh:
-for _offset they just use unsigned
-and for _drops they use atomic_uint32_t
What's the difference? (why use unsigned for one and atomic for the other?)

Tx,
Koen



On 8/2/06, Jason Haas <jjhaas at gmail.com> wrote:
> Additionally, the uintX_t declared variables are fixed bit lengths, while
> int, long, char, ... may vary in bit length on different architectures.
>
> Jason
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>