Martin v. L=F6wis wrote: > "M.-A. Lemburg" <mal@lemburg.com> writes: >=20 >=20 >>>+ #ifndef Py_USING_UNICODE >>>+ abort(); >>>+ #else >> >>Shouldn't this be a call to Py_FatalError() with a proper >>error message ? >=20 >=20 > What is the guideline for when to use abort, and when to use > Py_FatalError? Looking at the code for Py_FatalError(), I'd say always use this instead of calling abort directly, except maybe for situations where you don't want anything printed. --=20 Marc-Andre Lemburg CEO eGenix.com Software GmbH _______________________________________________________________________ eGenix.com -- Makers of the Python mx Extensions: mxDateTime,mxODBC,... Python Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
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