check_mongen_order shouldn't be compiled into release builds

This function is only used during development, so if it's included
in a release build, the compiler will warn that it's never used.
This commit is contained in:
Alex Smith
2026-05-02 17:47:25 +01:00
parent 82bb085616
commit 16ff591153
+3 -1
View File
@@ -17,7 +17,6 @@ staticfn int align_shift(struct permonst *);
staticfn int temperature_shift(struct permonst *);
staticfn boolean mk_gen_ok(int, unsigned, unsigned);
staticfn int QSORTCALLBACK cmp_init_mongen_order(const void *, const void *);
staticfn void check_mongen_order(void);
staticfn void init_mongen_order(void);
staticfn boolean wrong_elem_type(struct permonst *);
staticfn void m_initgrp(struct monst *, coordxy, coordxy, int, mmflags_nht);
@@ -1777,6 +1776,8 @@ cmp_init_mongen_order(const void *p1, const void *p2)
return difficulty1 - difficulty2;
}
#if (NH_DEVEL_STATUS != NH_STATUS_RELEASED)
staticfn void check_mongen_order(void);
/* check that monsters are in correct difficulty order for mkclass() */
staticfn void
check_mongen_order(void)
@@ -1799,6 +1800,7 @@ check_mongen_order(void)
}
}
}
#endif
/* initialize monster order for mkclass */
staticfn void