Complete.Org: Mailing Lists: Archives: freeciv-dev: October 2002:
[Freeciv-Dev] Re: Path-finding in the presence of danger
Home

[Freeciv-Dev] Re: Path-finding in the presence of danger

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: rf13@xxxxxxxxxxxxxxxxx
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Path-finding in the presence of danger
From: Gregory Berkolaiko <Gregory.Berkolaiko@xxxxxxxxxxxx>
Date: Fri, 4 Oct 2002 16:48:24 +0100 (BST)

On Fri, 4 Oct 2002 rf13@xxxxxxxxxxxxxxxxx wrote:

> > We have rather different attitudes to the subject.  You seem to prefer to 
> > have many call-backs, while I would rather have one which does it all.
> > For this particular proposal,
> >     int get_extra(int x, int y, int curent_extra, void *data)
> > provides for the desired freedom.
> 
> I removed the extra_cost2 callback because there was no need for
> it. So while I agree with you that this calculation can be made more
> flexible I want to ask: so we know such situations? Is it worth it?
> Adding this extra flexibility is done in some hours. No problem.

I can imagine some situations but you are right, we can add it in a matter 
of hours when a need arises.

> The above case can't work since ECOT may only depend on the position.

I am not sure I understand you here.  Why ECOT "may only depend on the 
position"?  Because you postulated so?  Don't indulge in solipsism please 
:)

> The more I think about it the more I like the slim interface I
> proposed in the mail I answered Ross. Nothing on our code would. We

"Nothing on our code would"?
Please explain.

> would just rip the code of the path_finding.c and move it into
> path_finding_tools.c. So we would get three real layers (algorithm,
> callbacks with the freeciv logic and end-user like AI or agents).

Please elaborate or give a link to your email.

G.



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