🚀 go-pugleaf

az915@freenet.carleton.ca (William G. Royds) writes:

> > > > > Where does 'foo' come from
> > > > File: jargon.info, Node: foo, Next: foobar, Prev: fontology, Up: = F =
> > > > :foo: /foo/  1. /interj./ Term of disgust.  2. Used very
> > > > [3 pages of fooey deleted]
> > > Sheesh. What have you got on "bar"?
> > File: jargon.info, Node: bar, Next: bare metal, Prev: banner, Up: = B =
> > :bar: /bar/ /n./  1. The second {metasyntactic variable},
> >    after {foo} and before {baz}.  "Suppose we have two
> >    functions: FOO and BAR.  FOO calls BAR...." 2. Often
> >    appended to {foo} to produce {foobar}.
>   Actually the original term was from the Second World war and was a
> description of what happened to a plane hit by ack-ack fire (anti
> aircraft guns). THe term was fubar (F*cked Up Beyond All Recognition)
> with the first part Fu (F*cked Up) becoming foo by early lisp hackers.

As the 'foo' post explained, 'foo' has a much richer ancestory than
the common conception that it comes from 'fubar'.  I do exppect,
however, that the use of 'bar' as the second metasynactic variable
does come from the fubar usage.  Nevertheless, I suggest that
interested parties read the Jargon File themselves, at
  http://www.ccil.org/jargon

-- 
http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu
All my opinions are my own, not the Free Software Foundation's.

Second law of programming:
Anything that can go wrong wi
sendmail: segmentation violation -- core dumped