From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: bug in infantry building a base which is already started
Date: Wed, 26 May 2004 00:00:00 -0000 [thread overview]
Message-ID: <l03130300bcd98b98f2ce@[212.181.162.155]> (raw)
In-Reply-To: <Pine.LNX.4.44.0405251917030.11020-100000@leon.phy.cmich.edu>
>Yes, but, a journey of a 1000 miles begins with a first step, to
>quote an old professor of mine.
>
>If we work on weeding out the direct unit accesses as we encounter
>them in the non-action code, then we will be in better shape when
>(and I suppose, if) the time comes to make the transition to true
>client-server. This is the philosophy I have been operating
>under, anyway. Otherwise, unit views don't mean too much to me in
>some cases.
It would probably be a good idead in that case to make the unit views work
more like real units. I took some steps in that direction last spring when
I added occupant-transport relationships and garbage collection to the unit
view code. But there are still very significant differences not only
between the unit and unit view structures, but also in how they are
handled. Like the hash table.
Hans
next prev parent reply other threads:[~2004-05-26 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 3:45 Jim Kingdon
2004-05-24 20:00 ` Eric McDonald
2004-05-25 3:33 ` Eric McDonald
2004-05-25 21:53 ` Hans Ronne
2004-05-25 22:02 ` Hans Ronne
2004-05-25 22:27 ` Eric McDonald
2004-05-25 23:14 ` Hans Ronne
2004-05-25 23:28 ` Eric McDonald
2004-05-26 0:00 ` Hans Ronne [this message]
2004-05-26 21:00 ` Overwatch and Counterbattery? Elijah Meeks
2004-05-26 21:35 ` Hans Ronne
2004-05-27 2:17 ` Eric McDonald
2004-05-25 22:14 ` bug in infantry building a base which is already started Eric McDonald
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='l03130300bcd98b98f2ce@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=mcdonald@phy.cmich.edu \
--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).