I find that it is best, when you free() a pointer, to also set the pointer to NULL. So have your DESTROY method croak if the pointer is already NULL. Then your test script can call DESTROY by hand and then let the object go out of scope and trap the error: 

    my $fail= eval {
        {
            my $obj= My::Mod->new();
            $obj->DESTROY();
        }
        1
    };
    print "not "
        unless $fail  &&  $@ =~ /destroyed NULL/;
    print "ok 19\n";

[download]

I hope that eval traps XS-based croak().

And, of course, this won't work in Perl 6 if it doesn't implement reference counting.

        - tye (instruction at 0xBADC0DE5 tried to read 0x00000000)

In reply to (tye)Re: Testing DESTROY Methods? by tye
in thread Testing DESTROY Methods? by Zaxo

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.