use Perl

• Nothing to add (Score:1)

  by pdcawley (485)

  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.
  • Re:Nothing to add (Score:2)

    by jdavidb (1361)

    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
  • Re:Nothing to add (Score:1)

    by exeunt (319)

    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.
• personal programming idioms. (Score:1)

  by anithri (288)

  @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...