in reply to Catching the death of a weak reference

Heh - I'd vote for Lazy - my wife says it's a character flaw :-)

In the interests of getting it on the CPAN, I'll paraphrase my old comp-sci prof:

  1. Get it working.
  2. Get it working right.
  3. Get it working fast.

Just my $0.03CDN

  • Comment on Re: Catching the death of a weak reference

Replies are listed 'Best First'.
Re^2: Catching the death of a weak reference
by nothingmuch (Priest) on Oct 28, 2004 at 14:16 UTC
    I currently have it working.

    As for working right - that's arguable. From the outside it appears to be working right - all the interfaces are implemented correctly. But it does have this "leakish" behavior.

    My problem is that the only way i know to getting it working right on the inside too, is so contradictory to point 3, it might be contradictory point 1 as well.

    What I need to know is whether there is a way to get it working right and fast, simultaneously, using knowlege I cannot afford to learn right now, because the overhead of learning it is too high, for a probable no.

    Provided I have a good direction, and a positive or at least optimistic answer I will consider it a good excuse to finally learning to muck with perl internals.

    Lastly, is being lazy, or voting for lazy the character flaw?


    zz zZ Z Z #!perl