Re: A check for 'break' or ^C would help a lot
J. Dashiell (dashiell@nadc.nadc.navy.mil)
Tue, 28 May 1996 17:01:16 -0400
In those situations where there's alot of messages and an operation if it's
run will likely take alot of time to complete perhaps a message to that
effect warning the user that if you continue with this operation it's likely
yarn will be finished in a week with a continue (y/n) prompt might help.
Probably not feasible for yarn to make estimates of the actual time requirements
and estimates really aren't the point here anyway.
I know when I write programs I know are going to perform very slowly because
of limited hardware and unlimited records I usually suggest that the user
goes to lunch and checks back after that for results once a process starts.
Btw, that's how Bill Gaits did so well as a programmer.
Whenever he was asked when will this project be
completed? his answer was invariably it won't be completed for at least
another x weeks or months.
// EOJ
jude <dashiell@nadc.nadc.navy.mil>
Shop at the mobias strip mall: always on the same side of the street,
Klein Glassworks, torus donuts, projective airlines, Escher Galleries, Fine Gifts, ETC.