Thanks GrandFather, that may well be what i am looking for. I can will try to incorporate tests into the objects so that they can make sure that the code refs haven't gone funky and that the data the objects hold hasn't changed either.
I guess subclassing a specialised My::Mod::WithTests class, which includes testable data and expected code ref output, would be the best way to do this? then i can include a few 'testable' objects in the larger collection. Or would a run_tests() method be enough (again including specialised test data and expected ouput)?
I'll take into account perrin's advice too, see if i can't avoid this whole thing somehow. Or at least strip down the serialized data to a simpler format, only including the key data, and have a new_from_skeleton() method...
Thanks everyone for your input!
Just a something something...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||