From 997a4469a2022461f5fe011bd7d0843d6dd6c5de Mon Sep 17 00:00:00 2001 From: Steven Noonan Date: Tue, 13 Oct 2009 03:05:10 -0700 Subject: fix 'DEBUG' macro usage consistency Sometimes we were doing #if DEBUG and others we were doing #ifdef DEBUG. If we mix both, we have problems: If the DEBUG macro isn't defined, the statement '#if DEBUG' doesn't really make sense logically, because 'DEBUG' has no value. And if we '#define DEBUG 0', then the '#ifdef DEBUG's become true statements. The easiest fix is to swap out the #ifs with #ifdefs. Signed-off-by: Steven Noonan --- crawl-ref/source/beam.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crawl-ref/source/beam.cc') diff --git a/crawl-ref/source/beam.cc b/crawl-ref/source/beam.cc index e2815833cc..98379be9c2 100644 --- a/crawl-ref/source/beam.cc +++ b/crawl-ref/source/beam.cc @@ -1494,7 +1494,7 @@ void bolt::initialise_fire() if (range == -1) { -#if DEBUG +#ifdef DEBUG if (is_tracer) { mpr("Tracer with range == -1, skipping.", MSGCH_ERROR); -- cgit v1.2.3-54-g00ecf