Was FORTRAN buggy 4321
On Tue, 26 Sep 2006 11:29:58 -0500 in alt.folklore.computers, Charles
TECO wasn't too bad if you programmed using indented source with comments like any other language, then "compiled"-squished the source .TES to .TEC, removing comments and white space. MUNG was your friend, and somewhat safer than interactive editing, if testing. You had to be very careful with loops and conditionals in interactive sessions, and list changes as you finished each line (0TT), or the whole buffer (HT) at the end, before saving.
My first real TECO program generated all Saturday dates in a five year range, using a 10cps ASR33 dialed into an On Line Systems TOPS-10 machine. The output was needed for a Critical Path Method project scheduling package run on the same system. At some point the project manager realized that one subcontractor's workers had to work six days a week to meet their deadlines. The solution was to make the weekend Sunday only, and all the other subcontractors' workers had to be given every Saturday off as a holiday. Didn't know if there were other languages on the system, if we had access to them, or instructions for use; just knew TECO was available and could deal with it.
-- Thanks. Take care, Brian Inglis Calgary, Alberta, Canada
part of the issue was that the official-strategic communication product was SNA ... which had effectively large master-slave paradigm...
fake address use address above to reply
Alt Folklore Computers from Newsgroups