A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-January/107279.html below:

[Python-Dev] Checking input range in time.asctime and time.ctime

[Python-Dev] Checking input range in time.asctime and time.ctime [Python-Dev] Checking input range in time.asctime and time.ctimeR. David Murray rdmurray at bitdance.com
Thu Jan 6 16:47:25 CET 2011
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 tm_year <
>> 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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4