> > - safe version of PyErr_Format > > +0 on that, but what do I know. Don't know if it's actually safe ;) >=20 > -0 on that, I'd rather use snprintf when available, sprintf when not. strange argument. why is it okay to crash Python on Windows, pure SUSv2 platforms, pure ANSI C platforms, etc? besides, snprintf doesn't do the same thing as my PyErr_Format replacement... </F>
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