"put try/catch blocks around any "complicated" destructors, silently absorbing any exceptions that might occur. The rationale simply being – that, since you are dying anyway, nobody really cares about you anymore."

What an absolutely backwards, ignorant and absurd thing to do. Your assumption that nobody cares is equally as asinine.

If your destruction routines are that "complicated", fix them! If you're wrapping the destructor of someone else's code, DON'T hide information they may relay. You have no idea what someone is doing in there. What if it's designed to reset system components because if they don't get reset, the system may be damaged permanently after program restart? Yes, I have destructors that do these things.

"It might cause memory leaks but the bottom line is that the thing keeps going."

Wow. "Let's consume memory needlessly and permanently even though it's no longer needed or in use. Letting the program continue is more important than the stability of the system as a whole!".

Dumbfounding.


In reply to Re^2: Debugging DESTROY calls in forking application by stevieb
in thread Debugging DESTROY calls in forking application by cavac

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.