One option is to patch Data::Dumper on the fly. I did this in
IPC::SharedCache so I could make my release before a bug in
IPC::ShareLite was released. Something like (untested):
no warnings 'redefine';
if ($Data::Dumper::VERSION < NEXT_VERSION) {
*Data::Dumper::some_method =
sub {
# replacement code here
};
}
The upside here is that only users of your module will see the new Data::Dumper behavior, and you can document it in your module. The downside is that if Data::Dumper doesn't get your patch by NEXT_VERSION then you'll need to change your module to take it working.
All that said, I think you should probably take a step back here. Are you sure you need to change Data::Dumper? It's an old and rather stable module. If it doesn't do what you want maybe you need to sub-class it or replace it with something more suited to your needs.
-sam
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.