From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: hronne@comhem.se, <xconq7@sources.redhat.com>
Subject: Re: The border between fiction and reality
Date: Thu, 19 Aug 2004 15:46:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0408191129450.9219-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <200408190637.i7J6bZc03815@panix5.panix.com>
On Thu, 19 Aug 2004, Jim Kingdon wrote:
> > However, a different situation arises with move-unit commands, all of which
> > eventually end up in advance_into_cell. At this point we are committed to
> > moving, and we have to know what real units are present in the destination
> > cell.
>
> Well, to me that means there should be an advance action, so that the
> decision between overrun and move (and the other choices, like
> capture) are in the action, rather than outside it.
I agree. After looking at code again, I saw what Hans was actually
having an issue with. I would recommend the 'advance' action as
well. The concept is really not much different than what we have
been discussing regarding attempted attacks and attempted fire;
this is simply an attempted move. And again, the distinction is
handled at the action level, and so there is no requisite that
unit pointers be used to divine something ahead of time at the
task level.
Eric
prev parent reply other threads:[~2004-08-19 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 15:14 Hans Ronne
2004-08-18 21:10 ` Eric McDonald
2004-08-19 11:25 ` Jim Kingdon
2004-08-19 11:57 ` Hans Ronne
2004-08-19 17:03 ` Jim Kingdon
2004-08-19 19:43 ` Hans Ronne
2004-08-19 15:46 ` Eric McDonald [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0408191129450.9219-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=hronne@comhem.se \
--cc=kingdon@panix.com \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).