So if get the point, there is no easy way to test whether something can be treated as a hash ref (for instance) short of trying to do so. So the best way to test is to try and catch any exceptions that indicate failure.
The alternative is that you use B to ask whether you *really* has a hash reference and overload to ask whether your object of some other type has %{} dereferencing magic. This exposes you to more magic than you want to have to know about.

use B 'svref_2object'; use overload (); sub bad_idea { my $thing = shift @_; local $@; # Protect against $@ stomping return # Is a real hash reference eval { svref_2object( $thing )->isa( 'B::HV' ) } # Pretends to be a hash reference or ( overload::Overloaded( $thing ) and overload::Method( $thing, '%{}' ) ); }

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊


In reply to Re^6: RFC: Perl meta programming by diotalevi
in thread RFC: Perl meta programming by bennymack

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.