public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Stan Shebs <shebs@apple.com>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Reduced Visibility Table?
Date: Tue, 02 Dec 2003 04:46:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0312012306520.3913-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <3FCBCF93.7070406@apple.com>

On Mon, 1 Dec 2003, Stan Shebs wrote:

> Heh, it's very messy coding to have a unit be there and not there at the 
> same time.
> AI, UI, plan, and task code should only ever iterate over the stack of 
> images,
> never over the real units. Action prep sometimes needs to know, 
> sometimes not,
> which is part of the messiness.

As long as we have Stan's attention :-) and we are talking about 
plan and task code, I do recall Hans seeking comment on the 
rationale for broadcasting tasks in the network code. Also, while 
we're on the subject, why is there some entanglement between what 
I believe Peter referred to as "referee code" and "AI code"?

Eric

  parent reply	other threads:[~2003-12-02  4:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 22:35 Elijah Meeks
2003-12-01 23:18 ` Hans Ronne
2003-12-02  1:09   ` Elijah Meeks
2003-12-02  4:02     ` Hans Ronne
2003-12-01 23:23 ` Bruno Boettcher
2003-12-01 23:27   ` Lincoln Peters
2003-12-01 23:43     ` Stan Shebs
2003-12-02  0:30       ` Hans Ronne
2003-12-02  0:54         ` Lincoln Peters
2003-12-02  0:58           ` Hans Ronne
2003-12-02  4:46       ` Eric McDonald [this message]
2003-12-02  4:04     ` Eric McDonald
2003-12-02  4:16       ` Eric McDonald
2003-12-02 20:56       ` Hans Ronne
2003-12-03  2:41         ` Eric McDonald
2003-12-03  3:04           ` Lincoln Peters
2003-12-03 21:13             ` Eric McDonald
2003-12-01 23:32   ` Hans Ronne
2003-12-02 15:04     ` Bruno Boettcher
2003-12-02 19:57       ` Emmanuel Fritsch
2003-12-03  2:12         ` Hans Ronne
2003-12-03  2:22       ` 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=Pine.LNX.4.44.0312012306520.3913-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=shebs@apple.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).