I thought whitespaces doesn't really matter. This is not python :D
No, whitespace doesn't mostly matter, but maybe you invoked the MACRO precompiler features ( perlrun ) or loaded a source filter via PERL5OPT or something like that, something that inserted an extra stray curly brace or square bracket
Did you save a copy of the broken one? Did you use Data::Dumper; use Path::Tiny; dd( path( $file )->slurp_raw ) ;
| [reply]
[d/l] |
Yes I had use Data::Dumper; before "use - this broken module". Why would that be a problem?
| [reply] |
Yes I had use Data::Dumper; before "use - this broken module". Why would that be a problem? I didn't say that (what do you think the rest of the code was about?). I asked if you employed ddumperBasic debugging checklist Basic debugging checklist item 4 , to see what the bytes are in the file
| [reply] |
I suggested perltidy because it will sometimes complain about missing braces, etc, and give you the line number that was unmatched in a way different than perl -c will in the log file. You are indeed most correct that white space doesn't matter. But that doesn't mean that a silly typo doesn't creep in now and again. :)
On time, cheap, compliant with final specs. Pick two.
| [reply] |