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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a74f519f90450e39
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-11-07 09:24:22 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.204!attbi_feed4!attbi.com!rwcrnsc51.ops.asp.att.net.POSTED!not-for-mail
Message-ID: <3DCAA1C5.9080900@attbi.com>
From: "Robert I. Eachus" <rieachus@attbi.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Test
References: <3dc8f30f$1@baen1673807.greenlnk.net>
 <usj8ab1ppoj725@corp.supernews.com>
 <YMhy9.904$vy1.514669790@newssvr11.news.prodigy.com>
 <s%hy9.197$fX5.934@news13-win.server.ntlworld.com> <3DC9C1BB.1050500@acm.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 24.61.239.24
X-Complaints-To: abuse@attbi.com
X-Trace: rwcrnsc51.ops.asp.att.net 1036689861 24.61.239.24 (Thu,
 07 Nov 2002 17:24:21 GMT)
NNTP-Posting-Date: Thu, 07 Nov 2002 17:24:21 GMT
Organization: AT&T Broadband
Date: Thu, 07 Nov 2002 17:24:21 GMT
Xref: archiver1.google.com comp.lang.ada:30546
Date: 2002-11-07T17:24:21+00:00
List-Id: <comp.lang.ada>

>> Where do "foo", "bar" and "baz" come from?
> 
> 
> I don't know. Foobar is supposed to come from fubar, an acronym for 
> fv<ked up badly all round, but this is the 1st I've heard of baz.

Foo actually comes from the TMRC (Tech Model Railroad Club) at MIT.  In 
the early 60's there was probably ten times as much effort put into the 
automatic switching network than into the actual HO gauge layout.  It 
was all run with telephone stepper switches (moving in 1964 to a 
crossbar switch)  From any of about a dozen control stations, you could 
dial the number of a control block on the layout and take control of a 
train sitting there.  The system would follow the train from block to 
block, avoid moving you into another occupied control block and all that 
good stuff.  If you were approaching a set of points from one of the 
legs, the points would be set correctly.  If you were approaching from 
the other direction you could dial the number of the points/switch and 
change the direction you would take.

There was of course a large display on the wall with the status of the 
layout, showing occupied blocks and switch settings, etc.  There was 
also a display with a character and two digits that showed error 
conditions like two trains headed for each other, and so on.  The two 
digits were the block or switch number associatied with the conflict. 
F-codes were used for more general problems, and F00 was an indication 
that the system had crashed--the logic had tried to resolve an 
unanticipated condition.

Since most TMRC hackers were also into computers, and many worked 
part-time on Project MAC, in the MIT AI lab, or with the TX0 and PDP-1 
machines in Building 16, FOO became the first metavariable.  BAR became 
the second metavariable due to the pun with FUBAR.  AFAIK, the third 
metavariable was always FOOBAR, while the fourth was either FOOB or BAZ. 
  BAZ is again a homonym--what comes after BAR? BAS.  How do you 
pronounce it?  BAZ.  So use BAZ and avoid the confusion which can come 
from reading (or thinking) about a program verbally and typing something 
other than what was meant.

Why was FU never used as a metavariable? Same problem, there is a 
tendancy to read it as eff-you.  While often a sentiment you wanted to 
express to the computer when debugging, it could again lead to misspellings.