From: Lincoln Peters <sampln@sbcglobal.net>
To: Xconq list <xconq7@sources.redhat.com>
Subject: Possible bug in side_can_research
Date: Fri, 10 Sep 2004 19:17:00 -0000 [thread overview]
Message-ID: <1094789127.4338.103479.camel@localhost> (raw)
When I re-wrote ai_plan_research, I had assumed that the
side_can_research function would return false for advances that have
already been researched. However, having run advances.g several times
under AI control, I've found that the AI will frequently select an
advance that it already has discovered. And I have not found any logic
errors in the new ai_plan_research function.*
Would it be reasonable to modify side_can_research so that it returns
false for advances that the side already has? Or would it be better to
place the necessary code in ai_plan_research instead?
* This is not to imply that no logic errors exist in the new version,
just that if they do exist, they are currently undiscovered.
---
Lincoln Peters
<sampln@sbcglobal.net>
BOFH excuse #251:
Processes running slowly due to weak power supply
next reply other threads:[~2004-09-10 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 19:17 Lincoln Peters [this message]
2004-09-11 2:49 ` Eric McDonald
2004-09-11 19:27 ` Lincoln Peters
2004-09-11 19:54 ` 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=1094789127.4338.103479.camel@localhost \
--to=sampln@sbcglobal.net \
--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).