>> Except that it is very useful to be able to use structures to map
>> over device register sets.
> It might be "useful" to you, but it's just flat out wrong for
> portable code, especially of course if you're using bitfields,
[...]
> 	#define offsetof(type,memb) ((size_t)&((type *)0)->memb)
> They do go on to warn that an implementation need not permit such use
> of the null pointer constant in that fashion, but I've never
> encountered a compiler implementation that disallowed it.....

Does anyone else see the irony of these being juxtaposed in the same
message?  Especially since "map[ping] over device register[s]" is
approximately the last place you have to worry about portability to
every compiler on the planet?

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B