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/2002-January/019703.html below:

[Python-Dev] Mixing memory management APIs

[Python-Dev] Mixing memory management APIs [Python-Dev] Mixing memory management APIsNeil Schemenauer nas@python.ca
Wed, 30 Jan 2002 08:28:07 -0800
Michael Hudson wrote:
> Modified Files:
> 	_curses_panel.c 
> Log Message:
> Oh look, another one.
> 
> 2.2.1 candiate (he says, largely talking to himself :)

> *** 192,196 ****
>       Py_DECREF(po->wo);
>       remove_lop(po);
> !     PyMem_DEL(po);
>   }
>   
> --- 192,196 ----
>       Py_DECREF(po->wo);
>       remove_lop(po);
> !     PyObject_DEL(po);
>   }

I think we have to break down and do what Tim suggests.  Ie make:

    free == PyMem_DEL == PyObject_DEL == PyObject_FREE == ...

pymalloc needs to use a completely new set of APIs.  The only problem I
see is coming up with names.  NEW, MALLOC, REALLOC, RESIZE, and DEL are
all taken.  Any suggestions?

  Neil



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