4 ms·
The IBM mainframe high-speed printers from decades ago made it possible to overprint the same line several times. My memory of this was fuzzy, but I believe wh
by m463 6y ago
The IBM mainframe high-speed printers from decades ago made it possible to overprint the same line several times.
My memory of this was fuzzy, but I believe when you sent lines to the printer, there was a control code in the first column to have normal printing or to overprint the last line:
|
v
line-of-text
+this-overprints-previous-line
There were all kinds of things that you could do that were non-optimal, like overprinting lots and lots of stuff until it wore out the paper or making many things print simultaneously. If you did too much, the printer would stop and open the cover - think a 5x5x8 box opening its lid.
To be clear - these were basically chain saws with hammers behind the chain all controlled by software.
- dbcurtis 6y agoyes. the printers had 132 columns. you sent a buffer of 133 chars, the first being carriage control. blank was line feed, i forget what was page-eject/form-feed (1?? memory fuzzy). + was overprint. As a student, I had a part-time job as an I/O clerk. (feed the card reader, file printouts). We disabled overprint on student jobs because it caused a lot of headaches from bugs. Form feed in an infinite loop was enough hassle. The original IBM printer did not document + for overprint, it was the result of a logic optimization in the controller and someone discovered it. So IBM installed a field change order that disabled that function, but included a switch that for an additional monthly fee would upgrade your printer to a model that supported it. The automatic openning of the lid at the end of a box of paper destroyed coffee cups on a regular basis.
- unixhero 6y ago"Field change order" So essentially a change order carried out by IBM in "the field", meaning your university. Interesting ;)
- mnaydin 6y agoI am reminded of Fortran 77. In Fortran 77, the first character of a record to be printed out determined vertical spacing as follows: Blank One line 0 Two lines 1 To first line of next page + No advance
- reaperducer 6y agoOverstrike was essential in the early days. Some printers didn't have question marks, so we used a capital P, instead. Some didn't even have a space character, or world trim them out, so a lowercase b (for "blank") with a / on top of it would represent a space.
- dannyw 6y agothat’s crazy. Did you do P and a . over stroke for question Mark? Or just, like thisP
- reaperducer 6y agoLike thisP. But text was precious, so questions were often condensed into one word. "Do you want to get pizza?" Became simply "PizzaP"
- hyperdimension 6y agoJust curious: does that happen to have anything to do with lisps' -p for predicate suffix?
- reaperducer 6y agoI really have no idea, as I've never worked with Lisp.
- lambda 6y agoHuh. That's an interesting question. I looked up the original LISP paper (http://www-formal.stanford.edu/jmc/recursive.pdf http://www-formal.stanford.edu/jmc/recursive.pdf), and it looks like the -p convention hadn't been established yet at that point, none of the predicates have that suffix in the paper. But it does say this: (LABEL, SUBST, (LAMBDA, (X, Y, Z), (COND ((ATOM, Z), (COND,(EQ, Y, Z), X), ((QUOTE, T), Z))), ((QUOTE, T), (CONS, (SUBST, X, Y,(CAR Z)), (SUBST, X, Y, (CDR, Z))))))) This notation is writable and somewhat readable. It can be made easier to read and write at the cost of making its structure less regular. If more characters were available on the computer, it could be improved considerably.[4] ---- [4] 1995: More characters were made available on SAIL and later on the Lisp machines.Alas, the world went back to inferior character sets again—though not as far back as when this paper was written in early 1959 So at the very least, some of the syntactic conventions of LISP were mostly due to limited character sets at the time. Trying to binary search through history to figure out when the -p convention was introduced, I checked the original Scheme paper (https://web.archive.org/web/20171201033214/http://repository.readscheme.org/ftp/papers/ai-lab-pubs/AIM-349.pdf https://web.archive.org/web/20171201033214/http://repository...), which has some examples in Scheme as well as implementation code in MacLISP. It looks like the predicate convention wasn't really strongly established at that point; in a few places, they use variables with a trailing `?` in the Scheme code, but I don't see any use of a predicate convention in the MacLISP implementation code. Going back a bit, I do see the predicate convention mentioned in an Interlisp manual from 1974, but without an explanation of its origin (http://bitsavers.trailing-edge.com/pdf/xerox/interlisp/Interlisp_Reference_Manual_1974.pdf http://bitsavers.trailing-edge.com/pdf/xerox/interlisp/Inter...). A MacLISP manual from the same year also mentions the -p convention, but not its origins. So looks like it had been firmly established by 1974: http://www.softwarepreservation.org/projects/LISP/MIT/Moon-MACLISP_Reference_Manual-Apr_08_1974.pdf http://www.softwarepreservation.org/projects/LISP/MIT/Moon-M... Going back further, the LISP 1.5 manual (second edition, 1965, though the printing was from 1979) has a number of numeric predicates with the -p suffix, but it does not make note of the suffix convention (https://archive.org/details/lisp15programmer00john/page/26/mode/2up?q=predicate https://archive.org/details/lisp15programmer00john/page/26/m... , free registration required). It does use a lot of language discussing "predicate" and use the term "p position of a conditional expression" (https://archive.org/details/lisp15programmer00john/page/22/mode/2up?q=predicate https://archive.org/details/lisp15programmer00john/page/22/m...), so the use of "p" for "predicate" rather than "?" seems to be somewhat well established. LISP 1.5 had a very restrictive syntax for identifiers, they were just alphanumeric. So, I'm going to say that while it's possible that the usage of P for this purpose comes from substitutiong P for ?, all of the sources I've found seem to indicate that it stands for "predicate."
- beezle 6y agoWhy do I still have this odd desire to have my own personal line printer? Something about reading printouts on green and white paper (sacriledge to flip it over to the white side) always made debugging easier. And the sound is the best!
- pacaro 6y agoEven better some of the early printers (e.g. IBM 1132) had a wheel for every character position, all on a common axle, so you told the printer which character you wanted, then set bit fields in memory for which positions to strike, then wait for interrupt and repeat until you have printed all the characters that were used on that line, then told it to advance. The timing for this was finicky, to the point that the cheap 1130 wasn't capable of doing this fast enough, which was solved by IBM by making it run at a higher clock speed when at interrupt level 1. As you might imagine many of those machines spent a lot of time at interrupt level 1 doing things unrelated to printing