Well, that would address /one/ of my concerns, that is it would not just die on an unblessed reference. But it doesnt address the other issues I mentioned.

Why not?

my $regexp = qr/Some Regex/;
warn "It's regexpable!" if $regexp->DOES( 'REGEX' );

my $subref = sub { ... };
warn "It's invokable!\n" if $subref->DOES( 'CODE' );

my $overloaded = Way::OverLoaded->new();
warn "It's indexable/keyable/invokable\n" if $overloaded->DOES( 'ARRAY
+' )
                                          && $overloaded->DOES( 'HASH'
+ )
                                          && $overloaded->DOES( 'CODE'
+ );

[download]

Those may not be the best role names, but I hope the idea is clear.

In reply to Re^5: I don't understand UNIVERSAL::DOES() by chromatic
in thread I don't understand UNIVERSAL::DOES() by rlb3

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.