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_def.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_def.cc')
-rw-r--r-- | crawl-ref/source/los_def.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/crawl-ref/source/los_def.cc b/crawl-ref/source/los_def.cc index 1367a22bf4..7c1515a0e3 100644 --- a/crawl-ref/source/los_def.cc +++ b/crawl-ref/source/los_def.cc @@ -48,7 +48,7 @@ void los_def::init_arena(const coord_def& c) { center = c; arena = true; - set_bounds(circle_def(LOS_MAX_RADIUS, C_SQUARE)); + set_bounds(circle_def(LOS_RADIUS, C_SQUARE)); } los_def::~los_def() |