Re^3: doubts about Data::Dumper output

I'm not sure what bug you're talking about. The fact that Data::Dumper can't dump code references is documented:

"Data::Dumper" cheats with CODE references. If a code reference is encountered in the structure being processed (and if you haven't set the "Deparse" flag), an anonymous subroutine that contains the string '"DUMMY"' will be inserted in its place, and a warning will be printed if "Purity" is set.

لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

Comment on Re^3: doubts about Data::Dumper output

Replies are listed 'Best First'.
Re^4: doubts about Data::Dumper output by Anonymous Monk on Oct 07, 2014 at 07:23 UTC
I'm not sure what bug you're talking about The weird `do{my $o}` .... I forgot to realize that $Data::Dumper::Deparse wasn't turned on ... yeah	[reply] [d/l]
Re^5: doubts about Data::Dumper output by LanX (Saint) on Oct 07, 2014 at 07:45 UTC
Not that weird, it returns a lexical scalar variable for the slot. But without polluting the namespace with the dummy name $o, cause the scope is limited. Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :)}	[reply]
Re^6: doubts about Data::Dumper output by Anonymous Monk on Oct 07, 2014 at 08:35 UTC
Not that weird, it returns a lexical scalar variable for the slot. But without polluting the namespace with the dummy name $o, cause the scope is limited. Sure its weird to write `do { my $o}` when it could write `undef` or "DUMMY" or "fix" or "V: $VAR1->{a}" or any other string	[reply] [d/l] [select]
Re^7: doubts about Data::Dumper output by LanX (Saint) on Oct 07, 2014 at 09:07 UTC
Re^8: doubts about Data::Dumper output by Anonymous Monk on Oct 07, 2014 at 09:19 UTC