Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!ll-xn!ames!sdcsvax!net1!graifer From: graifer@net1.ucsd.edu (Dan Graifer) Newsgroups: comp.sys.mac Subject: Appropriate Language in Programming (Was: Re: System Error 33) Message-ID: <3445@sdcsvax.UCSD.EDU> Date: Mon, 13-Jul-87 23:25:35 EDT Article-I.D.: sdcsvax.3445 Posted: Mon Jul 13 23:25:35 1987 Date-Received: Wed, 15-Jul-87 02:27:08 EDT References:<3519@ecsvax.UUCP> <3785@osu-eddie.UUCP> Sender: nobody@sdcsvax.UCSD.EDU Reply-To: graifer@net1.UUCP (Dan Graifer) Organization: UCSD Office of Academic Computing Lines: 26 In article <3785@osu-eddie.UUCP> elwell%tut.cis.ohio-state.edu@osu-eddie.UUCP (Clayton Elwell) writes: >In article <3519@ecsvax.UUCP> wmcb@ecsvax.UUCP (William C. Bauldry) writes: >>>Stump the Stars: what dis the "DS" in "DSErrCode" originally stand for? >>> >> >>... there's also this thought of D*** S*** that I've >>... >is headed by the comment "Deep Sh*t Error Alerts". I can see why the >published version was switched to say "Dire Straits," but I still think the >original was more in the spirit of what you feel when you see a system bomb >while debugging... > > >Clayton Elwell Apple isn't the only place where code has to be "cleaned up" for final release. I recall working with the Burroughs large system MCP (a multi- tasking multiprocessor operating system) in the early 70s. There were two procedures to separate a daughter task from a parent task, a process called "forking": the mother f_____g and the father f______g procedures. The rumour I heard was that these names stayed there until some corporate client complained. Dan Graifer graifer@net1.UCSD.EDU Disclaimer: Nobody ever listens to me anyways; Why should they start now?