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 jnoller, mark.dickinson, pitrou, ronaldoussoren
Date 2010-08-13.13:28:11
SpamBayes Score 0.00066512433
Marked as misclassified No
Message-id <1281706094.19.0.302062665982.issue9586@psf.upfronthosting.co.za>
In-reply-to
Content
BTW, as far as I can tell from the standard (see e.g., section 6.5.9p2 of

www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf

), comparison between a pointer and an integer gives undefined behaviour, except in the case where the integer can be interpreted as a null pointer constant (which is not the case here).  I'm assuming that the reason that gcc only gives a warning here rather than an error is that its general machinery can only tell that we're comparing an integer with a pointer, which *could* be valid C if that integer is 0.

So I do think this should be fixed, one way or another.
History
Date User Action Args
2010-08-13 13:28:14mark.dickinsonsetrecipients: + mark.dickinson, ronaldoussoren, pitrou, jnoller
2010-08-13 13:28:14mark.dickinsonsetmessageid: <1281706094.19.0.302062665982.issue9586@psf.upfronthosting.co.za>
2010-08-13 13:28:12mark.dickinsonlinkissue9586 messages
2010-08-13 13:28:11mark.dickinsoncreate