Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!security!genrad!decvax!harpo!seismo!hao!hplabs!sri-unix!CS.Temin@UTEXAS-20.ARPA
From: CS.Temin@UTEXAS-20.ARPA
Newsgroups: net.ai
Subject: Re: Artificial Humanity
Message-ID: <13832@sri-arpa.UUCP>
Date: Sun, 20-Nov-83 03:24:00 EST
Article-I.D.: sri-arpa.13832
Posted: Sun Nov 20 03:24:00 1983
Date-Received: Tue, 22-Nov-83 03:29:32 EST
Lines: 25

From:  Aaron Temin <CS.Temin@UTEXAS-20.ARPA>

I found these errors really interesting.

I would think a better rule for Eurisko to have used in the bounds
checking case would be to keep the bounds-checking code, but use it less
frequently, only when it was about to announce something as interesting,
for instance.  Then it may have caught the flip-flop error itself, while
still gaining speed other times.

The "credit assignment bug" makes me think Eurisko is emulating some
professors I have heard of....

The person bug doesn't even have to be bug.  The rule assumes that if a
person is around, then he or she will answer a question typed to a
console, perhaps?  Rather it should state that if a person is around,
Eurisko should ask THAT person the question.  Thus if Eurisko is a
person, it should have asked itself (not real useful, maybe, but less of
a bug, I think).

While computer enthusiasts like to speak of all programs in
anthropomorphic terms, Eurisko seems like one that might really deserve
that.  Anyone know of any others?

-aaron