So you don't expect anyone to ever test their modules against overloaded input? I disagree that comparisons should default to being x-ray comparisons just because they are part of a test module. I'm more likely to test that the output from two invocations produce the same apparent output than that they result in identical internal structures. The former is an important aspect of a module, while the latter shouldn't really matter.

Update: In a private message, diotalevi notes that he meant that the test should usually be normal but that there should be a way to do the x-ray test. My reponse is that to do the x-ray test you temporarilly unbless the overloaded items, but I'm shocked to see that Scalar::Util doesn't have unbless(). There is a non-core module, Acme::Damn, but that nearly doesn't solve the problem (being non-core and also XS and further Acme::). But I suspect that temporarilly blessing into a non-overloaded package would be a "fix", but I haven't tested such.

- tye        

In reply to Re^8: Recursively traverse two data structures and test for match (testing / overload) by tye
in thread Recursively traverse two data structures and test for match by TedPride

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.