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 member to see if it is the target; if it is, end the iteration
The only kind of program I can think of which doesn't have a plan is one built by some
kind of learning system which
adjusts the outputs based on samples of inputs.
In fact, one of the characteristics of high performance programmers (as versus merely
experienced programmers) is that
they probably have a larger collection of plans or have more flexible plans.
That's how they're able to do the refactering. Programmers with less plan capability
are less able to do the re-organization;
if all you know is the simple "find" plan above, then you are less able to, say,
recognize that the original "find" loop could
be replaced by an indexed lookup.
Ruven Brooks
- Automatic footer for [EMAIL PROTECTED] ----------------------------------
To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss
To join the announcements list, mail [EMAIL PROTECTED] subscribe announce
To receive a help file, mail [EMAIL PROTECTED] help
This list is archived at http://www.mail-archive.com/discuss%40ppig.org/
If you have any problems or questions, please mail [EMAIL PROTECTED]
