Re: Data::Dumper and printf

The issue is that printf expects a format string as the first argument (thus the 'f'). When you pass the array reference to Dumper, it returns a single string, which printf interprets as its format string. When you pass Dumper the array, it returns an array of strings and so printf thinks the first argument is the format, and thus only prints that.

#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.

Comment on Re: Data::Dumper and printf Select or Download Code

Replies are listed 'Best First'.
Re^2: Data::Dumper and printf by Anonymous Monk on Nov 21, 2012 at 05:50 UTC
And using printf like that forms a class of vulnerabilities known as format string vulnerabilities, in C and other languages that pass to the libc function directly. The interpreted languages generally don't and are safe from this. It causes a denial of service (program crash) most of the time.	[reply]
Re^2: Data::Dumper and printf by Trihedralguy (Pilgrim) on Nov 21, 2012 at 00:05 UTC
That is what I was thinking, but I wasn't completely sure that this was the answer to the question. One of my peers asked me why this was working the way it was and I wasn't 100% sure what the correct answer was. Thank you for your explanation.	[reply]
Re^3: Data::Dumper and printf by LanX (Saint) on Nov 21, 2012 at 17:05 UTC
one confusing thing is that printf and sprintf have different prototypes! `DB<108> prototype "CORE::sprintf" => "\$\@" DB<109> prototype "CORE::printf" => undef` [download] so `sprintf @array` will evaluate the array in scalar context, such that now the number of elements will be interpreted as format string... Cheers Rolf	[reply] [d/l] [select]