Michael Hudson <mwh@python.net> writes:

Neil Schemenauer <nas@python.ca> writes:

...

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?

And then change all the current uses of PyObject_Del to the new API? What would that buy us? Unless I misunderstand we *have* to do something different to remove an object as opposed to freeing raw storage (GC, for example).

I agree we have too many preprocessor macros, but I don't think we can have free == PyObject_DEL.

No, I take that back... -- Just point your web browser at http://www.python.org/search/ and look for "program", "doesn't", "work", or "my". Whenever you find someone else whose program didn't work, don't do what they did. Repeat as needed. -- Tim Peters, on python-help, 16 Jun 1998