Follow-up Comment #5, patch #4388 (project freeciv): > I noticed that REQ_RANGE_WORLD is still handled separately from > REQ_RANGE_ALLIANCE, REQ_RANGE_TEAM in some is_xxx_in_range() > functions despite being supported by players_in_same_range(). > Is that intentional? On a quick look, I think most of the places where REQ_RANGE_WORLD is handled separately takes advantage of quicker ways of getting information at world range (num_world_buildings() etc). The only exception I noticed where the code could be simplified without losing this was is_techflag_in_range().
_______________________________________________________ Reply to this item at: <http://gna.org/patch/?4388> _______________________________________________ Message sent via/by Gna! http://gna.org/ _______________________________________________ Freeciv-dev mailing list Freecivemail@example.com https://mail.gna.org/listinfo/freeciv-dev