Jack Jansen writes: > One point to think of, with the malloc cleanup: how many places are there > where Python allocates something that is passed to some packages which then > takes ownership of it (and ultimately free()s it)? And the other way around? > > For these cases we should probably continue to use malloc()/free() to be on > the safe side. Yes; that would be the only way to handle that if it doesn't provide any way to control the deallocation. And if it does, you can still use malloc & free. Good enough for me! -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> Corporation for National Research Initiatives
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