public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: Elijah Meeks <elijahmeeks@yahoo.com>, xconq7@sources.redhat.com
Subject: Re: Wrecking Revisited
Date: Sun, 06 Jun 2004 06:11:00 -0000	[thread overview]
Message-ID: <1086502104.1485.157.camel@localhost.localdomain> (raw)
In-Reply-To: <l03130302bcd555cf48bf@[212.181.162.155]>

On Sat, 2004-05-22 at 13:11, Hans Ronne wrote:
> >I think designers would be better served if the code
> >simply vanished any disallowed unit without reporting
> >an error.  I can't see much reason for it to work like
> >it does, but maybe I'm missing something.
> 
> My recollection is that this is how the wrecking code should work, i.e.
> wrecks that cannot belong to their assigned side should simply vanish. So
> you may have found a bug. Or possibly an overzealous run warning.

This should now be fixed as part of the wrecking overhaul I just
committed to the repository. I actually had most of it done by noon of
last Sunday, but then got hung up on a bug when I was working on a
simple game to demonstrate the changes. Frustrating....

The behavior is now:
If the new unit type can remain on the same side as the old type, then
leave it there.
If not, then, if the new unit type can belong to the side that wrecked
it, then change its side to the wrecking side.
If not, then, if the new unit type can belong to the independent side,
then change its side to the independent side.
If not, then make it vanish.
In any case, the unit is no longer left on a disallowed side, and no
errors are reported.

Eric

  reply	other threads:[~2004-06-06  6:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22  0:21 Curses and SDL apps for Windows and MacOS Hans Ronne
2004-05-22  2:27 ` Elijah Meeks
2004-05-22  2:43   ` Eric McDonald
2004-05-22 10:16   ` Hans Ronne
2004-05-22 14:05     ` Hans Ronne
2004-05-22 17:14     ` Elijah Meeks
     [not found]       ` <1085247112.1485.405.camel@localhost.localdomain>
2004-05-22 17:39         ` Eric McDonald
2004-05-22 19:02           ` Wrecking Revisited Elijah Meeks
2004-05-22 19:13             ` Hans Ronne
2004-06-06  6:11               ` Eric McDonald [this message]
2004-05-23 20:23   ` Curses and SDL apps for Windows and MacOS Stan Shebs
2004-05-23 20:37     ` Eric McDonald
2004-05-23 20:45       ` Stan Shebs
2004-05-23 21:02         ` Eric McDonald
2004-05-23 21:28     ` Hans Ronne
2004-05-23 22:42       ` Elijah Meeks
2004-05-23 22:56         ` Hans Ronne

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=1086502104.1485.157.camel@localhost.localdomain \
    --to=mcdonald@phy.cmich.edu \
    --cc=elijahmeeks@yahoo.com \
    --cc=hronne@comhem.se \
    --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).