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 vstinner
Recipients mark.dickinson, vstinner
Date 2009-05-06.08:17:36
SpamBayes Score 3.2841346e-10
Marked as misclassified No
Message-id <1241597858.78.0.750914301331.issue5933@psf.upfronthosting.co.za>
In-reply-to
Content
> For the second, I don't understand why you want to
> compare the return result with RLIM_INFINITY:  PyInt_AsLong
> returns -1 to signal failure;  is there some guarantee that
> RLIM_INFINITY == -1 if it's defined?

rlim_t is an unsigned type. The idea of sign_warning_resource.patch 
was to make gcc quiet about signed/unsigned comparaisons.

RLIM_INFINITY is defined as (rlim_t)-1. But it looks that it's not 
clear, so I wrote another patch to fix the warnings.
History
Date User Action Args
2009-05-06 08:17:38vstinnersetrecipients: + vstinner, mark.dickinson
2009-05-06 08:17:38vstinnersetmessageid: <1241597858.78.0.750914301331.issue5933@psf.upfronthosting.co.za>
2009-05-06 08:17:37vstinnerlinkissue5933 messages
2009-05-06 08:17:37vstinnercreate