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

Showing content from https://mail.python.org/pipermail/python-dev/2000-February/002214.html below:

[Python-Dev] Malloc interfaced

• Previous message: [Python-Dev] Malloc interface (was: [Patches] Re: Garbage collection patches for Python (fwd)
• Next message: [Python-Dev] Malloc interfaced
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, 14 Feb 2000, Vladimir Marangozov wrote:
>...
> Agreed. So the concrete proposal is this, right?
> 
> (mymalloc.h)
> 
> ...
> #define PyMem_FREE(p)	free((ANY *)p)

Small nit:
  #define PyMem_FREE(p)	free((ANY *)(p))

(yes, the "bug" exists in 1.5.2, too)

> ...
> 
> #define PyMem_DEL(p)	PyMem_FREE(p)
> #define PyMem_XDEL(p)	PyMem_FREE(p)  /* obsolete */

Both of these would be obsolete.

Note that the PyMem_NEW/RESIZE/FREE macros are intended for internal use
by Python only. (move to a private header?)

Py_Malloc and friends, and PyMem_Malloc and friends are to be used by C
extensions (or embeddors).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

• Previous message: [Python-Dev] Malloc interface (was: [Patches] Re: Garbage collection patches for Python (fwd)
• Next message: [Python-Dev] Malloc interfaced
• 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