Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

exeunt (319)

  reversethis-{} {ta} {izaguf}

My perlmonks Personal Node []

Journal of exeunt (319)

Friday March 15, 2002
07:33 PM

What's the weirdest name you have given a variable name/sub?

[ #3580 ]

This journal made me think of typos in code, and then to reflect on werid variable names I've used.

Some are obvious, like $foo, $bar, $blah, $temp, $tmp.

Some of my favorites:
%HugeAssHash (later renamed to %hah)
&kludge(), &bugfix(), (the list could go on)

Anybody else have some to add to this list?

Updated: Forgot to enable comments, I think that should be a prefernce somewhere to always have it on, unless I am missing it.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • But if I came across any variables/functions with names like that during a code review, the perpetrator would have it explained to him in no uncertain terms that a repetition would be considered a Career Limiting Move.

    What you do in your own, private programs is, of course, your own look out, but I strongly recommend staying disciplined.
    • I never name anything with anything but a meaningful name, anymore. Even a list index. If I can't say what the thing is I'm writing code about, how can I write correct code for it?

      That sounds silly, but it's the case. If I spend ten minutes figuring out what to name the list index, I may save thirty minutes later when the code has grown more complex.

      Of course, I rarely use an index in Perl; I use foreach. But I apply the same principle everywhere I can.

      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • Oh, I understand all that now, and the &kludge was when I was a beginer, and the %HugeAssHash was more of a joke with my co-workers, in a throw away script.

      Of course, there is the other end of this spectrum, where you have &getPageAndParseItThenSaveIt(); function names, which do not really lend them selves to saving time. I've never been that verbose, but have seen it in other people's code.
  • @stuff and @junk are my standard temporary array and hash names. $this, $that, $other are standard scalars. and of course the file handles READ and WRITE...