Data::Dump::Streamer can be used to serialize subroutines and closures properly under sane scenarios. (Yes you can deliberately craft a set of closures that will not dump properly, but it should be quite rare in practice as it would require using unwise var naming practices in the first place.)

As for regular expressions, DDS can serilize them properly as well so long as they don't include (?{}) and (??{}). In other words regexes that arent closures are properly handled. Ill have to make a stab at handling regex closures in a future release.

PS: i think you meant "SCALAR" and "REF", there is no perl type "SCALARREF". :-)

---
$world=~s/war/peace/g

In reply to Re^2: Behaving appropriately based on ref() result by demerphq
in thread Behaving appropriately based on ref() result by qbxk

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.