diff options
| author | Adam Borowski <kilobyte@angband.pl> | 2012-06-24 17:02:19 +0200 |
|---|---|---|
| committer | Adam Borowski <kilobyte@angband.pl> | 2012-06-24 17:14:46 +0200 |
| commit | bf500ca0f0c03f9b47483a75c60910e70388e638 (patch) | |
| tree | e9bd0fa575222337ddf703b062481e95006ea856 /crawl-ref/source/los.cc | |
| parent | c702831a7453b0c4c2aed77e2d3b2fd7bb5cf1fd (diff) | |
| download | crawl-ref-bf500ca0f0c03f9b47483a75c60910e70388e638.tar.gz crawl-ref-bf500ca0f0c03f9b47483a75c60910e70388e638.zip | |
Remove #define LOS_MAX_RADIUS
Having both it and LOS_RADIUS is misleading, especially as they're
arbitrarily used. This distinction doesn't make sense anyway, as any
LOS changes need to be done at runtime, only the max matters during
compilation.
Diffstat (limited to 'crawl-ref/source/los.cc')
| -rw-r--r-- | crawl-ref/source/los.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/crawl-ref/source/los.cc b/crawl-ref/source/los.cc index eee99ec40f..bbb707f671 100644 --- a/crawl-ref/source/los.cc +++ b/crawl-ref/source/los.cc @@ -129,7 +129,7 @@ static void _handle_los_change(); void set_los_radius(int r) { - ASSERT(r <= LOS_MAX_RADIUS); + ASSERT(r <= LOS_RADIUS); _los_radius_sq = r * r + 1; invalidate_los(); _handle_los_change(); |