use Perl

• Here Here! (Score:1)

  by jk2addict (4946)

  I agree. A module should always use its own methods over accessing private data whenever possible. This is especially true for subs that clean data on the way in, or when using lvalues.
  
  A quick example... sub custnum(value) does sanity checking on the value passed in. Now, any code in that same module can save directly to $self->{customnum}, but they miss the sanity checking code.
  
  I think there is afine line in there. IT all depends on the data being set, and if there are any data manips/check that should
  • Re:Here Here! (Score:2)

    by Dom2 (2981)

    For me, it simply removes an extra pair of braces, thereby making the code read a lot more easily. All the rest are side benefits. :-)

    -Dom
• AKA... (Score:1)

  by LTjake (4001)

  ...Eating your own dog food.

  See Andy's post from late 2003 [perl.org]
• cheap overtime (Score:2)

  by jmm (276)

  When an hourly rate employee works overtime, it is typical that they get paid time-and-a-half or double time - i.e. (wage * 1.5) or (wage * 2.0).

  What kind of a sweat shop are you running that pays overtime hours at half the normal rate? (It sounds like a programming shop, except that there overtime hours get (wage * 0.0) :-)
  • Re:cheap overtime (Score:2)

    by Ovid (2709)

    Oops! Fixed, thanks.
• Outside-Out (Score:2)

  by bart (450)

  I don't know where you get the idea that Outside-In is the opposite of Inside-Out, as it is actually the same thing: something where the inside and the outside are swapped.
  
  The opposite of Inside-Out is Outside-Out, or Inside-In, or just plain and simple: "normal".