[Guido] > Also, I believe there once was an issue on Windows where a DLL > shouldn't call its own malloc, it should call Python's malloc (even if > they're both the system malloc!) for memory that Python might free, > and conversely it should call Python's free for memory that Python has > allocated, because the DLL might be using a different heap than the > Python core. Wrapper functions defined by the core that call the > core's malloc/realloc/free are the only solution here. > > I'm not sure if this is still an issue; I'm not even really sure it > was ever an issue; I recall learning this from reading the Tcl/Tk > sources. I'm just repeating this in the hopes Mark Hammond will notice it <wink>. i'm-not-a-windows-programmer-i'm-a-programmer-on-windows-ly y'rs - tim
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