summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/skills.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/skills.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/skills.cc')
-rw-r--r--crawl-ref/source/skills.cc3
1 files changed, 1 insertions, 2 deletions
diff --git a/crawl-ref/source/skills.cc b/crawl-ref/source/skills.cc
index 9249bf9f4e..cf58ab44c4 100644
--- a/crawl-ref/source/skills.cc
+++ b/crawl-ref/source/skills.cc
@@ -70,8 +70,7 @@ int calc_skill_cost(int skill_cost_level)
240, 248, 250, 250, 250, // 21-25
250, 250 };
- ASSERT(skill_cost_level >= 1);
- ASSERT(skill_cost_level <= 27);
+ ASSERT_RANGE(skill_cost_level, 1, 27 + 1);
return cost[skill_cost_level - 1];
}