Use NULL rather than 0. (#778)

There was few cases of using literal 0 instead of NULL in the context of
pointers.  While this was a legitimate C code, using NULL rather than 0 makes
the code clearer.
This commit is contained in:
Serhiy Storchaka 2017-03-23 17:53:47 +02:00 committed by GitHub
parent aefa7ebf0f
commit 0b3ec19225
8 changed files with 15 additions and 15 deletions

View file

@ -643,7 +643,7 @@ static void _pysqlite_step_callback(sqlite3_context *context, int argc, sqlite3_
aggregate_instance = (PyObject**)sqlite3_aggregate_context(context, sizeof(PyObject*));
if (*aggregate_instance == 0) {
if (*aggregate_instance == NULL) {
*aggregate_instance = _PyObject_CallNoArg(aggregate_class);
if (PyErr_Occurred()) {

View file

@ -434,7 +434,7 @@ PyMODINIT_FUNC PyInit__sqlite3(void)
PyDict_SetItemString(dict, "OptimizedUnicode", (PyObject*)&PyUnicode_Type);
/* Set integer constants */
for (i = 0; _int_constants[i].constant_name != 0; i++) {
for (i = 0; _int_constants[i].constant_name != NULL; i++) {
tmp_obj = PyLong_FromLong(_int_constants[i].constant_value);
if (!tmp_obj) {
goto error;