On 1 August 2011 14:08, Michael Mc Donnell <mich...@mcdonnell.dk> wrote: >> With the bitfields I'm not sure about stuff like endianess. My gut feeling >> would be to use bitmasks and shifts to separate a DWORD instead, but >> bitfields >> certainly look nicer. Beyond that endianess is a somewhat academic >> consideration with an API that's available on x86 only. So I'd say keep the >> bitfields. > > Ok good. That'll keep me from the pain of doing bit twiddling on a > little endian machine :-) > You can't do that, even on x86. Bitfield memory layout is undefined.
- Re: GSoC-2011: Implement Missing ... Dylan Smith
- Re: GSoC-2011: Implement Missing ... Michael Mc Donnell
- Re: GSoC-2011: Implement Missing Mesh Functions in Win... Stefan Dösinger
- Re: GSoC-2011: Implement Missing Mesh Functions in... Michael Mc Donnell
- Re: GSoC-2011: Implement Missing Mesh Function... Stefan Dösinger
- Re: GSoC-2011: Implement Missing Mesh Func... Stefan Dösinger
- Re: GSoC-2011: Implement Missing Mesh Functions in Win... Stefan Dösinger
- Wine and endianness GOUJON Alexandre
- Re: Wine and endianness David Laight
- Re: Wine and endianness GOUJON Alexandre
- Re: GSoC-2011: Implement Missing Mesh Functions in... Henri Verbeet
- Re: GSoC-2011: Implement Missing Mesh Function... Stefan Dösinger
- Re: GSoC-2011: Implement Missing Mesh Func... max
- Re: GSoC-2011: Implement Missing Mesh ... Henri Verbeet
- Re: GSoC-2011: Implement Missing ... max
- Re: GSoC-2011: Implement Missing ... Henri Verbeet
- Re: GSoC-2011: Implement Missing ... Michael Mc Donnell
- Re: GSoC-2011: Implement Missing ... David Laight
- Re: GSoC-2011: Implement Missing ... max
- Re: GSoC-2011: Implement Missing Mesh Functions in Win... Stefan Dösinger
- Re: GSoC-2011: Implement Missing Mesh Functions in... Stefan Dösinger