Don't use 0 as null pointer constant, part 1
Use NULL instead of 0, for clarity. Except in pointer comparisons; leave that to the next two commits.
This commit is contained in:
parent
a2ed975ec2
commit
615681ce16
51 changed files with 107 additions and 100 deletions
|
@ -128,7 +128,7 @@ paradrop(struct emp_qelem *list, coord x, coord y)
|
|||
att_combat_init(def, EF_SECTOR);
|
||||
def->x = x;
|
||||
def->y = y;
|
||||
if (att_abort(A_PARA, 0, def))
|
||||
if (att_abort(A_PARA, NULL, def))
|
||||
return RET_FAIL;
|
||||
|
||||
/* Show what we're air-assaulting, and check treaties */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue