Thanks for the sympathetic feedback John. I understand people are reluctant to change. It was just my intent to enlighten others as to the true background behind it.
So if it's not about to change, then I'll just have to cry $boo $hoo, $oye $vey. :)On Fri, Apr 15, 2016 at 8:05 PM, John McKown <john.archie.mckown@xxxxxxxxx> wrote:
Although people commonly use $foo $bar in examples, it is actually a misuse of a VERY rude acronym.The next time you need to make an example, please try being a little more original (or meaningful) with your variable names.
Anyone that has done time in the military, and other goverment agencies, has been introduced to the term fubar, which stands for "fouled up beyond all repair". Although fouled was replaced by another similar word where the 2nd, 3rd and 4th letters were substituted with other letters that gave more significance to it. Over time, fu was somehow misheard as foo, and coders commonly started using it in examples. Not Cool!I understand your dislike of this. But, in reality, the likelihood of it changing is very small. The same with SNAFU. Personally, except in a context such as this, I don't use them (I like using "bubba" for meaninglessness). And, even in examples, I think that properly named variables are a good idea. Let's face it "The one language all programmers use is cursing." A fact of life, even if quite improper in the past. And still improper in a business / professional setting, IMO.
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.In the above instance, I fear this is a fantasy. [sigh]--How many surrealists does it take to screw in a lightbulb? One to hold the griffon and one to fill the bathtub with brightly colored LEDs.
Maranatha! <><
John McKown
--
Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.![]()
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
