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

Showing content from https://mail.python.org/pipermail/python-dev/2002-March/020561.html below:

[Python-Dev] PyMem_Realloc corner case

• Previous message: [Python-Dev] proposal: add basic time type to the standard library
• Next message: [Python-Dev] PyMem_Realloc corner case
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I just got bit by the following:

On Windows, PyMem_Realloc() doesn't seem to work as advertised in
  http://www.python.org/doc/current/api/memoryInterface.html

In particular, "if n is equal to zero, the memory block is
resized but is not freed, and the returned pointer is non-NULL".

In Objects/object.c, lines 1878-1896, PyMem_Malloc() and
PyMem_Realloc() seem to try to guarantee this behavior.
Somehow it isn't working for me.

Does this mean MALLOC_ZERO_RETURNS_NULL should be defined
in PC/pyconfig.h?  Or do I have an off version of the CRT
that causes problems nobody else has <sigh>?

## Jason Orendorff    http://www.jorendorff.com/

• Previous message: [Python-Dev] proposal: add basic time type to the standard library
• Next message: [Python-Dev] PyMem_Realloc corner case
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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