Re^2: Data::Dumper output

It is therefore highly probable as everyone else has surmised that you have accidentally stringified $request at some point in the code you have not shown.

Stupid, Stupid, Stupid me!!!

I was trying to print with:

print Dumper %$request . "\n";
[download]

Removing the concatenated return character gives...

$VAR1 = '_content';
$VAR2 = 'visibility=HASH(0x26db708)&specificContent=HASH(0x26c2398)&li
+fecycleState=PUBLISHED&author=urn%3Ali%3Aperson%3AGKiAGefMOA';
$VAR3 = '_uri';
$VAR4 = bless( do{\(my $o = 'https://api.linkedin.com/v2/ugcPosts')}, 
+'URI::https' );
$VAR5 = '_headers';
$VAR6 = bless( {
                 'content-type' => 'application/x-www-form-urlencoded'
+,
                 'content-length' => 121,
                 'hash(0x26db3a8)' => undef,
                 '::std_case' => {
                                   'hash(0x26db3a8)' => 'HASH(0x26db3a
+8)'
                                 }
               }, 'HTTP::Headers' );
$VAR7 = '_method';
$VAR8 = 'POST';
[download]

Sorry for having a senior moment...

Comment on Re^2: Data::Dumper output Select or Download Code

Replies are listed 'Best First'.
Re^3: Data::Dumper output by parv (Parson) on May 08, 2021 at 11:28 UTC
It is therefore highly probable as everyone else has surmised that you have accidentally stringified $request at some point in the code you have not shown. ... I was trying to print with: `print Dumper %$request . "\n";` [download] Removing the concatenated return character gives... ... To continue to use `\n`, use a list with `print` ... `# Need to use "Dumper()" else "\n" will be swallowed by "Dumper ... ;" + print Dumper( ... ), qq[\n];` [download]	[reply] [d/l] [select]
Re^4: Data::Dumper output by Bod (Parson) on May 08, 2021 at 12:27 UTC
To continue to use `\n`, use a list with `print ...` Yes. Although I'd use a separate line for clarity `print Dumper $data_structure; print "\n";` [download] I just feel that is clearer and less prone to the sort of error I created.	[reply] [d/l] [select]
Re^5: Data::Dumper output by afoken (Chancellor) on May 08, 2021 at 16:00 UTC
To continue to use \n, use a list with `print ...` Yes. Although I'd use a separate line for clarity `print Dumper $data_structure; print "\n";` [download] Just use say: `say Dumper $data_structure;` [download] `say` outputs a trailing newline unless the arguments already contain a trailing newline. I just feel that is clearer and less prone to the sort of error I created. I'm no Lisp guy, but using a few more brackets helps to avoid ambiguity and misunderstandings between humans and computers. If you call a function or method, add brackets around the argument list. That's what I do, with only very few exceptions - mostly stuff that is listed in perlfunc, but behaves more like a keyword or a C macro (`__FILE__, __LINE__, __PACKAGE__, do, eval, package, use, require`) than like a function. I would have written ... `say Dumper($data_structure);` [download] ... in code for perl 5.10 and newer (i.e. with `use v5.10` in the file), or ... `print Dumper($data_structure),"\n"; # or print Dumper($data_structure)."\n";` [download] ... in code for older perls. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l] [select]
Re^6: Data::Dumper output by hippo (Bishop) on May 08, 2021 at 22:45 UTC
Re^7: Data::Dumper output by afoken (Chancellor) on May 09, 2021 at 09:51 UTC


Think about Loose Coupling
	PerlMonks