summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/target.cc
diff options
context:
space:
mode:
authorAdam Borowski <kilobyte@angband.pl>2013-06-08 20:29:11 +0200
committerAdam Borowski <kilobyte@angband.pl>2013-06-08 20:29:11 +0200
commitae1dc47dc5b5f48957eb44396ab153acc38ef712 (patch)
treedb3ffa00832ac001005b52002abc1650cd7f426b /crawl-ref/source/target.cc
parent258af752a1d6f6dc337c97e8ceabf26bcb974f31 (diff)
downloadcrawl-ref-ae1dc47dc5b5f48957eb44396ab153acc38ef712.tar.gz
crawl-ref-ae1dc47dc5b5f48957eb44396ab153acc38ef712.zip
ASSERT_RANGEs other than >= <.
Committing separately as I'm not sure whether checking, for example, ASSERT_RANGE(level, 1, 28) is that nice. Perhaps 27 + 1 could be better? Perhaps some other syntax?
Diffstat (limited to 'crawl-ref/source/target.cc')
-rw-r--r--crawl-ref/source/target.cc3
1 files changed, 1 insertions, 2 deletions
diff --git a/crawl-ref/source/target.cc b/crawl-ref/source/target.cc
index ab552ad010..c9f555b65a 100644
--- a/crawl-ref/source/target.cc
+++ b/crawl-ref/source/target.cc
@@ -687,8 +687,7 @@ targetter_thunderbolt::targetter_thunderbolt(const actor *act, int r,
origin = act->pos();
prev = _prev;
aim = prev.origin() ? origin : prev;
- ASSERT(r > 1);
- ASSERT(r <= you.current_vision);
+ ASSERT_RANGE(r, 1 + 1, you.current_vision + 1);
range2 = sqr(r) + 1;
}