I'm at a loss about any normal way to prevent Object::Deadly from having an ISA relationship with the UNIVERSAL class. I'm trying to protect myself against polluting things like UNIVERSAL::require (just search CPAN for other UNIVERSAL:: modules). Someone else has done sub UNIVERSAL::foo {...} and I want $my_obj->foo to fail to find UNIVERSAL::foo.

I've read all of CPAN's UNIVERSAL:: modules to get their current list of defined methods and have overrridden all of those. I've also used Devel::Symdump to search for any new, unknown methods at runtime. This is all patchwork because a new method could be defined right after I've finished doing my runtime checks for unknown methods.

Help?

$obj = bless {}, 'Bar'; $obj->violation; # succeeds with UNIVERSAL::violation package Bar; # no methods package UNIVERSAL; sub violation { ... }

In reply to ->isn't('UNIVERSAL') - stopping UNIVERSAL pollution? by diotalevi

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.