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/losglobal.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/losglobal.cc')
| -rw-r--r-- | crawl-ref/source/losglobal.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/crawl-ref/source/losglobal.cc b/crawl-ref/source/losglobal.cc index b1582ce2b3..80e2d334e0 100644 --- a/crawl-ref/source/losglobal.cc +++ b/crawl-ref/source/losglobal.cc @@ -24,7 +24,7 @@ static losfield_t* _lookup_globallos(const coord_def& p, const coord_def& q) if (!map_bounds(p) || !map_bounds(q)) return (NULL); coord_def diff = q - p; - if (diff.abs() > LOS_MAX_RADIUS_SQ) + if (diff.abs() > LOS_RADIUS_SQ) return (NULL); // p < q iff p.x < q.x || p.x == q.x && p.y < q.y if (diff < coord_def(0, 0)) |