in reply to Re^9: Where is the @ISA array?
in thread Where is the @ISA array?

Well if the answer is that you shouldn't use that module anymore -- what guarantee do we have that you guys won't discover a bug in parent, and release the bug fix as guardian or such?

Ruby and Smalltalk are really starting to look more and more attractive ...

Replies are listed 'Best First'.
Re^11: Where is the @ISA array?
by ikegami (Patriarch) on Jan 22, 2009 at 15:40 UTC
    Some bugs can't be fixed without breaking backwards compatibility. That goes for Ruby, Smalltalk and Mouse as well.
      Some bug fixes don't pollute the namespace and confuse users as to what to use.

      "Oh crap!"

      "Wha happen?"

      "I moved my parent class and now the error is not accurate."

      "I know -- we'll fix that and upload a whole new module, that'll teach 'em to use Perl!"

        Right. The docs for base should mention parent. Please submit a patch.

Re^11: Where is the @ISA array?
by Corion (Patriarch) on Jan 22, 2009 at 14:59 UTC

    You're trolling, but I'll bite. parent.pm won't accrue features like base did, and hence, the code will stay as small as it is. Hence bugs should remain fixable.

      Getting a little defensive now, are we? Can we have your guarantee on that? Not that bugs should remain fixable -- but rather that they will remain fixable?

      Maybe it is just a coincidence that this is your module? Ever heard of the word deprecation?

        I'm willing to sell you support for parent.pm, which includes the guarantee that bugs will be fixed (additional payment necessary to implement bugfix, fees payable monthly in advance, all prices excluding 19% VAT). But unless your money is on the table, I will stay with "should".