This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients Devin Jeanpierre, mark.dickinson, skrah, vstinner
Date 2013-05-01.20:00:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367438411.26.0.116092316366.issue17884@psf.upfronthosting.co.za>
In-reply-to
Content
> I don't understand why "#ifdef HAVE_UINT32_T" is tested, since configure ensures that uint32_t is always defined.

Take a look at the explanations in the autoconf file and in pyport.h.  No, configure does *not* always ensure that uint32_t is defined:  it does that only if the platform *doesn't* provide uint32_t, but does provide a 32-bit exact-width unsigned integer type (two's complement, no padding bits, etc. etc.).  Which is why we need to make a second check for the case that the platform *does* define uint32_t directly.
History
Date User Action Args
2013-05-01 20:00:11mark.dickinsonsetrecipients: + mark.dickinson, vstinner, Devin Jeanpierre, skrah
2013-05-01 20:00:11mark.dickinsonsetmessageid: <1367438411.26.0.116092316366.issue17884@psf.upfronthosting.co.za>
2013-05-01 20:00:11mark.dickinsonlinkissue17884 messages
2013-05-01 20:00:11mark.dickinsoncreate