Xref: utzoo rec.humor:18934 rec.humor.d:1641 comp.misc:5134 Path: utzoo!utgpu!watmath!clyde!att!cuuxb!dlm From: dlm@cuuxb.ATT.COM (Dennis L. Mumaugh) Newsgroups: rec.humor,rec.humor.d,comp.misc Subject: Re: Looking for Computer Folklore Summary: Committee on Utilitization of SymbolS Keywords: obscene words Message-ID: <2491@cuuxb.ATT.COM> Date: 15 Feb 89 00:41:52 GMT References: <530@tcsc3b2.UUCP> Reply-To: dlm@cuuxb.UUCP (Dennis L. Mumaugh) Followup-To: rec.humor Organization: ATT Data Systems Group, Lisle, Ill. Lines: 39 In article <530@tcsc3b2.UUCP> tcsc@tcsc3b2.UUCP (The Computer Solution Co.) writes: >There, on top of one of the trays of mail was a label with the >converted alumni record identifier. It read something like ... > > ------------------------------- > | 123FUCK69A4 MM 43210** | > | MISS INGRID BEASLEY EDU. 29 | > | ... | > >Thereafter, we were instructed to add the "DIRTY-WORD-ROUTINE" >which performed a table lookup of every word which a committee of >about a dozen of the raunchiest people in the department could >come up with. At the UoMd the computer center designed a new "fortran" compiler that had all of the "Features" of the Univac Fortran V and all of the features of MAD (Michigan Alogrithm Decoder). This included zero array subscripting, alpha-numeric labels and other goodies. I was decided to add a routine to censor the variables one could use. It was called CUSS for something like Committee on Utilization of SymbolS. It would give a diagnostic when it encountered the obscene symbol used and then continue as if the symbol hadn't been defined. One day a proferssor was using the system under demand mode (similar to time sharing but not quite) and had typed in a program and gotten the usual vomit from the terminal. In exasperation the professor (who was in immediate compile mode) typed: GOTO HELL HELL is not a suitable variable for use HELL is not defined. Shortly thereafter CUSS was removed. -- =Dennis L. Mumaugh Lisle, IL ...!{att,lll-crg}!cuuxb!dlm OR cuuxb!dlm@arpa.att.com