Article View: alt.folklore.computers
Article #124611Re: \r\n vs. CRLF (was Re: Why do we use '-- ' as a .sig separator ?)
From: newc... Joseph M. Newcomer
Date: Sat, 14 Feb 1998 00:00
Date: Sat, 14 Feb 1998 00:00
47 lines
2919 bytes
2919 bytes
I missed some of this thread, but I remember that most operating systems had a padding factor you set for each terminal, the number of NULs to follow a CR. We got a lot of throughput improvement by simulating the carriage position and sending the minimum number of NULs required to return it from where it was. Since it gave the illusion of faster response, the powers-that-be let us expend compute cycles on it (we finally determined that the cost of not processing the interrupt-completes on the unnecessary NULs paid for the additional cycles required to maintain the simulated carriage position). We once had a plotting program that drew graphs using characters on the terminal. I wrote an optimizer for it that took into account the carriage-return time, backspace time, and tab time. It put out a little calibration sequence (if you needed it) that put a bunch of vertial bars out using spaces between, then would move the carriage over, and send a HUGE number of NUL bytes, telling the user to push the "set tab" button (tabs were implemented by physical hardware on the 2741), then draw the same again with tabs and vertical bars. It would then ask for confirmation that the tabs were all set. Once it had this information, it would try to optimize each line relative to the last one by using the fastest drawing sequence possible. I usually got a factor of 3 or 4 output speedup; drawing the axis on the left was always the bottleneck. Then I discovered the "inverse line feed" character code and started rewriting it to take advantage of this, but never finished that project (the optimizations got a lot hairier). joe On 10 Feb 1998 19:53:51 GMT, an...@rmi.net (Andy Rabagliati) wrote: >According to Norman Brake <br...@austx.tandem.com>: >> >> Hmm... As I recall, there was a dash-pot on the left end of the >> carriage of ASR-33's. If its vent wasn't properly adjusted, either >> the carriage wouldn't get back to the left end in time (and more >> NUL's would be required) or it would bang the left end too hard. > >And heaven forbid that your paper tape somehow got into the >dashpot. It could jam the plunger so tightly you needed to >take the thing apart. > >Cheers, Andy! Joseph M. Newcomer newc...@flounder.com http://www3.pgh.net/~newcomer
Technical Details
Message-ID:
<350f18ad.870013892@206.210.64.12>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<6anoq6$8a3$1@news3.tufts.edu> <B103E64796685257D@hearsay.demon.co.uk> <hnsngr-ya023180000902980212550001@news.sirius.com> <34DF4BD9.B0A8D1C@austx.tandem.com> <6bqb8f$8tl$1@news1.rmi.net>Show Full Headers
Complete Article Headers
From: newc...@flounder.com (Joseph M. Newcomer) Subject: Re: \r\n vs. CRLF (was Re: Why do we use '-- ' as a .sig separator ?) Date: 1998/02/14 Message-ID: <350f18ad.870013892@206.210.64.12> X-Deja-AN: 325127227 References: <6anoq6$8a3$1@news3.tufts.edu> <B103E64796685257D@hearsay.demon.co.uk> <hnsngr-ya023180000902980212550001@news.sirius.com> <34DF4BD9.B0A8D1C@austx.tandem.com> <6bqb8f$8tl$1@news1.rmi.net> Mime-Version: 1.0 Organization: Pittsburgh OnLine, Inc. Newsgroups: alt.folklore.computers Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit