use Perl

• It's even more fun in DESTROY methods (Score:1)

  by Phred (5358)

  A couple years ago I tracked down a bug in DBIx::Librarian [cpan.org] where database handles were hanging around and causing trouble. Granted, the context I was using it in wasn't straight forward, but here's what the fix turned out to be:

  sub DESTROY {
      my ($self) = @_;
  
  -   disconnect $self if $self->is_connected;
  +   $self->disconnect if $self->is_connected;
  }

  The author turned around a new release really fast, but it's a reminder to me to always use the direct syntax.
• couldn't agree more (Score:2)

  by TeeJay (2309)

  I've never used nor liked indirect object syntax, it is much less clear, and makes even less sense in non-english languages.

  --
  
  @JAPH = qw(Hacker Perl Another Just);
  print reverse @JAPH;
• Doc Patches (Score:1)

  by chromatic (983)

  My favorite is reading code at Perl Monks that mixes different constructor invocation styles.

  Are you up for patching the documentation of the most egregious offenders? I can think of a few places in the Perl core that need re-education.
• problem is (Score:1)

  by educated_foo (3106)

  ## The problem is that you didn't use enough of it!
  
  use Test::More tests => 1;
  
  sub Foo::bar { 23 }
  ok can Foo "bar"
  
• The Fix (Score:2)

  by Ovid (2709)

  As an aside for anyone reading this who didn't know it, you can fix this with a unary plus:

  ok +Foo->isa("bar");

  But yet, indirect object syntax is very, very annoying.
• My only use of it (Score:1)

  by Alias (5735)

  I hate ...
  
      new Object(...); ... but for reasons I don't really understand I love ...
  
      throw Exception(...);
  
  
• throw me (Score:1)

  by jk2addict (4946)

  I never use indirect syntax with one exception: exceptions:
  
  throw My::Exception('Boom!');
  
  I should really get our of that habit. Then the game would be complete.