Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2001:
[Freeciv-Dev] Re: Pop cost patch (resending via bug system) (PR#897)
Home

[Freeciv-Dev] Re: Pop cost patch (resending via bug system) (PR#897)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Arien Malec <arien_malec@xxxxxxxxx>
Cc: Trent Piepho <xyzzy@xxxxxxxxxxxxx>, freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Pop cost patch (resending via bug system) (PR#897)
From: Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 22 Aug 2001 19:35:45 +0200
Reply-to: rf13@xxxxxxxxxxxxxxxxxxxxxx

On Wed, Aug 22, 2001 at 09:48:05AM -0700, Arien Malec wrote:
> 
> --- Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > > -int can_unit_add_to_city(struct unit *punit)
> > > +enum add_to_city_status unit_add_to_city_status (struct unit *punit)
> > 
> > What do think about {general,basic}_unit_add_to_city?
> 
> I think that implies that you are actually adding to the city, whereas you 
> want
> to know if you can, and if you can't, why...

Ok.

> It's obnoxiously long, but unit_add_to_city_attempt_result gets the idea
> across. I'l work on the extended patch to cleanup handle.... since changing 
> the
> function name is easy.

What about just changing the result type of can_unit_add_to_city? Like
can_unit_move_to_tile_with_reason?

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
  The trick is to keep breathing.


[Prev in Thread] Current Thread [Next in Thread]