[Python-Dev] Checking input range in time.asctime and time.ctime (original) (raw)
R. David Murray rdmurray at bitdance.com
Thu Jan 6 16:47:25 CET 2011
- Previous message: [Python-Dev] Checking input range in time.asctime and time.ctime
- Next message: [Python-Dev] Checking input range in time.asctime and time.ctime
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 06 Jan 2011 12:55:24 +0100, Victor Stinner <victor.stinner at haypocalc.com> wrote:
Le jeudi 06 janvier 2011 à 00:10 -0500, Alexander Belopolsky a écrit :
If calling specific system functions such as strftime with tmyear < 0 is deemed unsafe, we can move the check to where the system function is called. What do you mean by "unsafe"? Does it crash? On my Linux box, strftime("%Y") is able to format integers in [-2^31-1900; 2^31-1-1900] (full range of the int type).
I believe that we have had several cases where Windows "crashed" when out-of-range values were passed to the CRT that other platforms accepted.
-- R. David Murray www.bitdance.com
- Previous message: [Python-Dev] Checking input range in time.asctime and time.ctime
- Next message: [Python-Dev] Checking input range in time.asctime and time.ctime
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]