summaryrefslogtreecommitdiffhomepage
path: root/src/python/nxt_python.h
diff options
context:
space:
mode:
authorAndrew Clayton <a.clayton@nginx.com>2025-05-21 04:13:11 +0100
committerAndrew Clayton <a.clayton@nginx.com>2025-05-28 16:35:34 +0100
commit39f9121339559738cba5130c818e8920e1a2fa16 (patch)
tree47a9fa136b6e5c127fb6779e6d94de0f13ce5fcd /src/python/nxt_python.h
parent4fcbe9caf6639fa0fb5ca1663a5f32527b522580 (diff)
downloadunit-39f9121339559738cba5130c818e8920e1a2fa16.tar.gz
unit-39f9121339559738cba5130c818e8920e1a2fa16.tar.bz2
Use NULL instead of 0 as null pointer constant
GCC 15 enabled "-Wzero-as-null-pointer-constant" for C, which checks for places where '0' has been used as a null pointer constant. This showed a few places in Unit where we were using '0' instead of the more correct NULL macro. E.g. $ make -j4 EXTRA_CFLAGS=-Wzero-as-null-pointer-constant ... src/nxt_buf.c: In function ‘nxt_buf_mmap_alloc’: src/nxt_buf.h:192:21: error: zero as null pointer constant [-Werror=zero-as-null-pointer-constant] 192 | (bm)->start = 0; \ | ^ src/nxt_buf.c:135:9: note: in expansion of macro ‘nxt_buf_mem_set_size’ 135 | nxt_buf_mem_set_size(&b->mem, size); | ^~~~~~~~~~~~~~~~~~~~ Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
Diffstat (limited to 'src/python/nxt_python.h')
0 files changed, 0 insertions, 0 deletions