Nick Coghlan wrote: > The main problem is that many of these methods are not only used > internally, but are *also* part of the public C API made available to > extension modules. We want misuse of the latter to trigger exceptions, > not segfault the interpreter. But is it worth slowing everything down to check for this one particular error, among all the myriad ways a malfunctioning extension module can cause a crash? -- Greg
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