From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Possible bug in side_can_research
Date: Sat, 11 Sep 2004 19:54:00 -0000 [thread overview]
Message-ID: <41435191.7050609@phy.cmich.edu> (raw)
In-Reply-To: <1094879273.28085.18040.camel@localhost>
Lincoln Peters wrote:
>>Actually, there is a function to update the research vector and it gets
>>called whenever a topic is actually researched in the kernel run code.
>
> I'm a bit unclear on this. Do you mean that it selects a new advance to
> research at the beginning of every turn? I'd say that such behavior is
> rather inefficient.
It doesn't have anything to do with selecting new advances to be
researched. It just updates the list of which advances can be
researched, so that that list can be used elsewhere
('side_can_research', for example).
Eric
prev parent reply other threads:[~2004-09-11 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 19:17 Lincoln Peters
2004-09-11 2:49 ` Eric McDonald
2004-09-11 19:27 ` Lincoln Peters
2004-09-11 19:54 ` 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=41435191.7050609@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=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).