I have an experience that perl's own memory allocator is pretty good. I am curious why it is not *on* by default.
Apart from thread safety, there is the issue of "bug compatibility" with the system malloc when using buggy third party libraries. I've seen cases where third party libraries erroneously call free on a pointer that was not got from malloc, yet the system malloc is forgiving and does not crash. Now if you replace the system malloc with a pickier one that does crash ... In one way, that is good because you've just flushed out a bug in the third party library. OTOH, you may not have the source code for the third party library to fix it and the vendor may be unresponsive. Most third party libraries are tested primarily with the system malloc and work more reliably with it.

See also Using Perl's Malloc.

In reply to Re^2: Perl + Hoard ? by eyepopslikeamosquito
in thread Perl + Hoard ? by renodino

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.