Andrew Walenstein is raising important and useful points here.
As far as I'm concerned, whatever the mental representation of a program
might be, it's just a special case of mental representations in general. We
need to consider representations not only of Pascal programs but also of OO,
logic,
If by understanding a program one means holding the entire representation in
internal memory (short or long) at once, then I concede that one can never understand
a program; by similar reasoning, one can never understand history, medicine, or
psychology either. The use of some kind of
Derek,
Ugh, OO design. With so many competing ideas and each language
having different ways of structuring classes and inheritance, which seems
to influence so many peoples views on how to do it, I am staying well away
from this issue.
I think this is a bad idea. Love it or hate it, OO
An example of a simple plan is a simple find plan:
iterate through the set
test each set member to see if it is the target; if it is, end the
iteration
Most computer scientists would (hopefully) call this the linear search
algorithm -- and therefore be very worried about using
Andrew Walenstein wrote WRT Ruven Brooks:
in your own IJCAI'75 paper you proposed a model
in which an external goal stack partly replaces the internal goal stack
of the programmer (this model predates the Parsing-Gnisrap model by a
decade)
Yes, embarrassing, isn't it? And here am I
Robert,
Just seen your latest post. I did receive your first one, but wanted to
reread some of your paper before replying (my learning curve in
cognitive psychology has been very steep and I have probably forgotten
lots already).
I see that you are also a fan of Eiffel. What a well thought
Given the previous discussions on plan, as in plan of action, and plan, as in
schema or pattern, I am a little confused.
Are you using plan in both senses of the word here?
A plan can be discussed as a knowledge structure, or it can be
executed. I can tell you how I make breakfast,
In this way, the design of a program emerges, more than being
planned,
We should be careful not to confuse a term coined to describe a
specific research hypothesis in cognitive psychology - the
programming plan hypothesis - with the vernacular uses of the
individual words
I think there's some confusion here about what a programming plan is; it's like an
architect's plan for a house,
not a plan for accomplishing a task. Schema or pattern might be a alternate term.
An example of a simple plan is a simple find plan:
iterate through the set
test each set
