I really didn't know that. In my experiences (which are far from sophisticated), I don't remember a single time I regreted to use Data::Dump. Probably I haven't reached the edges that you mentioned. Given the zero size of the bug queue of the module and the general quality of modules by Gisle Aas, I thought it was quite a robust module. Maybe such examples of intolerance by Data:Dump should be transformed into bugs, so they get a chance of being fixed.
But it may be possible as well that things changed since the last time you gave a chance to Data::Dump. For instance, in the Changes file, we read:
Release 1.05 Improved track scalar references; dump() ended up recursing forever on some cyclic structures.
On the other hand, the usage we were telling about was as a debugging aid. If it fails, you can backup to Data::Dumper's ugly output without serious consequences.
In reply to Re^4: sprintf is printing unexepected output
by ferreira
in thread sprintf is printing unexepected output
by thezip
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |