a type ... doesn't inherit from ... but has all the proper behaviors of IO::File. Why should you reject it?

All you should care is that when you send close ... it closes. Hence, can is more appropriate than isa...

can tells me if by chance it has a method.
isa tells me it has all the proper behaviours by intent. Hence isa is almost always more appropriate than can.

I'm really not that sure where I sit in this argument, so I would be glad to read a clarification or rebuttal.

I got a laugh out of your example of first param a ref or class, as I've just forsworn the casual usage of

 bless $me, ref $self || $self;

as false laziness. And I drew a blank on any other ordinary usage.

In reply to Re: •Re: Re: Say no to ref $thing eq "Expected::Type" by rir
in thread Putting file contents into a scalar by ByteOrNybble

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.