Aahz <aahz@pythoncraft.com> writes: > I'm just picking a random spot to break into this thread. Last > go-round, I seem to recall a suggestion that pymalloc get a new API and > that anyone who wanted to use pymalloc would be forced to modify their > code. That would leave all currently working ways of spelling > malloc()/free() working. > > Is there some reason why we're not doing that? There is no code forthcoming to do that. Regards, Martin
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