From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109fba,baaf5f793d03d420 X-Google-Attributes: gid109fba,public X-Google-Thread: fc89c,97188312486d4578 X-Google-Attributes: gidfc89c,public X-Google-Thread: 103376,97188312486d4578 X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,6154de2e240de72a X-Google-Attributes: gid1014db,public X-Google-Thread: 10db24,4cf070091283b555 X-Google-Attributes: gid10db24,public From: Dennison Subject: Re: Goto considered really harmful Date: 1996/09/04 Message-ID: <322D0DC3.5820@iag.net>#1/1 X-Deja-AN: 178363395 references: <507oru$3lk@ns.broadvision.com> content-type: text/plain; charset=us-ascii organization: The Dennison Family mime-version: 1.0 newsgroups: comp.edu,comp.lang.ada,comp.lang.c,comp.lang.c++,comp.unix.programmer x-mailer: Mozilla 2.02 (Win95; I) Date: 1996-09-04T00:00:00+00:00 List-Id: Patrick Horgan wrote: > generator, so that upon detecting a goto statement it would generate a > full 132 columns of '-' characters, followed by a carriage return w/o > linefeed, and print this line about 50 times, on the same line of the > output. This had the effect of chopping right through the lineprinter > output at the goto statement, cutting the paper in half, which jammed the > lineprinter, requiring operator intervention. This *really* pissed the > operators off, and generally resulted in a high-decibel stream of abuse > directed at the poor slob of an undergrad who submitted the job. Most such institutional printers used to be of the "chain" variety. The REALLY nasty trick is to find the order that the letters appear on the printer's chain, and send that particular string to the printer. ...at least that's what I heard. -- T.E.D. email - mailto:dennison@iag.net homepage - http://www.iag.net/~dennison