use Perl

• That's not what I call 'inside-out' objects. (Score:1)

  by Abigail (26)

  People seem to think that Inside-Out Objects are about not letting other people touch your internals.

  They aren't.

  Inside-Out Objects solve two out of three problems* I have with traditional Perl OO:

  • It's not benefitting from enabling 'strict' (that is, no compile time checking of attribute names). Now you may say "I don't care about that, I have tests", but that just means you find both 'use strict' and 'use warning' fluff - after all, you have your tests.
  • In an inheritance tree, your implemenation is
  • Re: (Score:2)

    by Ovid (2709)

    I've evidently been wrong about IOO. Since the major problem I've faced has traditionally been encapsulation, that was the bit I've focused on. I will have to concede all your points. I just find that virtually every IOO implementation I've seen out there has been painful to work with, so I gave up and hope that solving the major problem I have might be good enough.
    • Re:That's not what I call 'inside-out' objects. (Score:1)

      by Aristotle (5147) <pagaltzis@gmx.de> on 2006.10.07 13:35 (#50865) Homepage Journal

      Hmm. For me, the visible difference between hash-based and inside-out objects is turning the following:

      my $self = shift;
      $self->{ bar };

      into this:

      my $self = refaddr shift;
      $bar{ $self };

      That seems hardly painful… but then, as MJD says, people are weird about syntax.

      Reply to This

      Parent