Funny variable names

[NeverHeardOfMe]

OK, so my textboxes are called txtThis, labels lblThat etc... call me puerile, but I stil smile when naming my File Upload conrtols fuOther.... even had one simply called fu2 once :)

[SpoonLord]

A project I used to work on had a module called 'cunit'. I was shocked when I first saw it.

[hoernchenmeister]

That calls for a BlastHymen() setter ;)

[BillW33]

One of my favorite silly variable names, written by a co-worker late at night, he named a boolean variable "JuatABool". :)

Just because the code works, it doesn't mean that it is good code.

[Stefan_Lang]

Well in your case it was just a matter of misreading, but in our application, some of the older code that used hungarian style names (i. e. names consisting of one or more abbreviated words) is consistently using the fragment 'anal' to denote something to do with 'analysis'. :doh:

[Julian Nicholls]

A lot of the active-low Power-on resets in the hardware I'm working on are called PORn too.

[BrainiacV]

A variable name I'll never forget was for a conveyor system I worked on with a friend. He had this naming convention of 8 characters max, using the normal names you'd like for the variable divided by the number of words gave you the number of characters to take from each word to create the variable name. Ex. PRINT SPOOLER became PRINSPOO and (my favorite) SHIPPING STATION CONTROL LOOP became SHSTCOLO (pronounce sheh sta co low). But another buddy wnt the other direction creating long names. One of his SmallTalk objects was called FireHunterSeekerBlowBackTo. In high school the PALD-8 Assembler for the DEC PDP-8 only allowed 6 character names. So when it came to having a counter, we started with COUNT, removed the vowels for CNT, started adding them back giving CONT and (I'll let you figure out the logical conclusion here).

Psychosis at 10 Film at 11

[Sound Dude]

I always use funny names for endless loops that wait for a condition then break. as in: const bool TheAZCardinalsStillSuck = true; while (TheAZCardinalsStillSuck) { ... } although the above example almost broke in 2008 - 2009, that code is secure this year.

[Slice24]

A colleague of mine used a variable called tibet. Once he was finished with the variable, he was then able to free(tibet)

[Alan Burkhart]

I downloaded some code a few years ago in which all the buttons in the interface had names like buttGo, buttSort, buttYes, buttNo...

Everybody SHUT UP until I finish my coffee...

[Joan Dineiro]

I had a collegue who had to write a credit app program. They named the database table CRAP and the columns in the table were all like CRAP_descript, CRAP_Type, etc. The boss made them rename everything. Bosses have no sense of humor

JodiYoda

[agolddog]

Similarly, I once worked for a firm where the servers were all Vegas casinos: MandalayBay, Venetian, etc, and the developer machines were all games: CaribbeanStud, Blackjack, etc. Not such a bad thing in a small shop, but it took a while to get up to remembering who was what.

[Steve Poulter]

I once had to deal with some MS-Basic code written by a bored kid who amused himself with variable names including:

dim eieio

(Think Old MacDonald...)

[JasonPSage]

So..everything in that system .... ahhaha

Know way too many languages... master of none!

[Tony Wright UK]

My favourite is a variable to hold the current time - SecsNow.

[Richard Hylton]

Not sure this is funny. Quite sure that it amused my small mind. I was working on a Purchase Order project and somehow variables ended up being named c3PO and extensions of that name.

RHYlton

[programmervb netc]

yorn What is that you ask...... Yes or No....dumb We also have a set of classes we call the blue classes because they all start with smrf. Bad thing is the little smurfs keep multiplying. Humble Programmer

[wizardzz]

Much like many engineering departments, there is only one female smurf. She must be quite busy if they are multiplying.

[Br Bill]

I worked on a build system for a company's huge software project. It had many options, and the variables inside the script files stored parameters for the build. For some reason, the variable names never exceeded 10 characters. For example, PROF_TOOL could contain the name of one of 3 different profiling tools, depending on the software language and version. In addition to PROF_TOOL, there were also: ARCH_TOOL - name of archiver COMP_TOOL - compiler LINK_TOOL - linker and my favorite, the code analysis tool : ANAL_TOOL . Everybody else at the company always spoke it to rhyme with "canal tool", but I took immature joy in always pronouncing it exactly the way it looks. "So which ANAL_TOOL were you using when you encountered the problem?" I'm a jerk.

[ghle]

wizardzz wrote:

have any examples

Financial software, Asset Manager = AssMgr In the old days (64KB was a lot), we had a program overlay on RAM that could reconfigure our machine tool software tables that resided in the RAM. The overlay program was call the Configurator. It was possible to reconfigure the system so that the RAM tables grew so large that they expanded into the Executive program area. We needed a flag for that, so that we could crash the executive program gracefully upon reload, instead of a run-away program. Name of the flag, of course, was FCEM 'Figurator Crashed Executive Memory. Yes, the FCEM flag (hard C, aka K). If it ever was TRUE, well, you were f....d. :-O

Gary