From what I know you are almost correct. adrianh has the problem but missed* in the turgid docs of perldoc:overload the implication of overload::StrVal which will return the pattern you specify. If that changed an endless chunk of code would break. Including Data::Dumper. You, or I or someone should post a documentation patch to make it permanent however.

Heres a more rigourous definition of a is_blessed test. 

$is_blessed = defined($x) && ref($x) && overload::StrVal($x) =~ /=/;

[download]
Incidentally for this check its faster but less idiomatic to say 
 
$is_blessd=defined($x) && ref($x) && (index(overload::StrVal($x),'=')>
+=0);

[download]
BTW, only if you choose to consider qr// constructs to be blessed then this test is fine. If you dont then you need something like 
$is_blessd=defined($x) && ref($x) && (index(overload::StrVal($x),'=')>
+=0) 
    && overload::StrVal($x)!~/^Regexp=SCALAR/;

[download]
PS: Im hoping that its obvious that you have to use overload; for all of this.

Cheers,

update:* I didnt mean to imply that he was wrong about the Scalar::Util approach. However it is an extra module and the code I mention should be fine without it. Although it is a lot faster to use than all of the above.

--- demerphq
my friends call me, usually because I'm late....

In reply to Re: stringified references by demerphq
in thread stringified references by rir

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.