Author vladris
Recipients docs@python, meador.inge, terry.reedy, vladris
Date 2011-09-30.17:19:10
SpamBayes Score 4.33768e-06
Marked as misclassified No
Message-id <1317403151.53.0.993055557363.issue12880@psf.upfronthosting.co.za>
In-reply-to
Content
Attached doc update against tip (though I still hope my patch for configurable allocation strategies will make it in). 

This is my first doc patch so let me know if I missed something. I am basically explaining that bit field allocation is compiler-specific and no assumptions should be made of how a bitfield is allocated. 

I believe this is the better thing to do rather than detailing how GCC and MSVC allocated their bitfields because that would just encourage people to use this feature incorrectly. Most bugs opened on bit fields are because people are toying with the underlying buffer and get other results than what they expect. IMO, when using bitfields one should only access the structure members at a high level and not go read/write the raw memory underneath.
History
Date User Action Args
2011-09-30 17:19:11vladrissetrecipients: + vladris, terry.reedy, meador.inge, docs@python
2011-09-30 17:19:11vladrissetmessageid: <1317403151.53.0.993055557363.issue12880@psf.upfronthosting.co.za>
2011-09-30 17:19:10vladrislinkissue12880 messages
2011-09-30 17:19:10vladriscreate