CS.Temin@UTEXAS-20.ARPA (11/20/83)
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