[Freeciv-Dev] (PR#3010) core dump from client air goto

["Jason Short via RT" <rt@xxxxxxxxxxxxxx>]

[glip - Fri Feb  7 20:53:56 2003]:

> > The solution is simple: don't set warmap_cost until right before
> it's used.
> 
> You chose a strange place to set things.  It will be reset (unless
> optimized) every time a better route is found -- and that could be
> lots.
> 
> Why not set it right after init_warmap is called?

To me it seems very natural to set it right before it it used.  But it
is true this means a couple of extra operations every now and then,
which could be significant since this code is called so often.

The alternative is to put the code right after warmap is created in
init_warmap.  But you must be sure you've caught all cases, and you must
also still initialize it at the beginning of the function.

jason