Re^2: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc

Thanks for the tip marto, when I run pp -x -o my_name.exe my_script.pl it runs the script in my command line output and then ultimately the .exe does work (even with every use on one line). I'll take that advice about the -x switch for pp in the future.

I didn't even know the .exe files created could be extracted like zip files, though I'm not sure I'm equipped with the know-how to go about debugging the differences and figuring out why one works over the other.

This isn't a crucial issue or anything since I did figure out a way to make it work (now I have two ways thanks to your -x suggestion), it just made me turn my head sideways with a funny look that simply adding the newline fixed the problem... very odd to me, since I wouldn't have thought that should matter at all.

Just another Perl hooker - But the purist monks keep telling me I should do it for love, not money.

Comment on Re^2: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc Select or Download Code

Replies are listed 'Best First'.
Re^3: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc by marto (Cardinal) on Jun 27, 2017 at 19:57 UTC
I'm mobile at the moment, so can't test further right now. However, a few things. Calling pp with `-vvv` this enables the highest level of verbose output. With the `-L` flag, provided with a file name this becomes the log for output, rather that stdout. See the documentation for various options. You could enable logging to discover the packaging process, compare the process for the different options and track down the reason from there. Similarly, extracting each exe into a directory will allow you to explore and compare the output. Comparing logs is probably easier :)	[reply] [d/l] [select]
Re^4: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc by perldigious (Priest) on Jun 27, 2017 at 21:28 UTC
Cool, and no worries, mobile or not it's nice of you to take a look at it at all. I always just use "`> some_log_name.txt`" at the end of any Windows command line input when I want to shunt to some log file instead of `STDOUT`, but of course if the script expects inputs you have to know them and the order they are expected since the prompts are shunted there as well. :-) Just another Perl hooker - But the purist monks keep telling me I should do it for love, not money.	[reply] [d/l] [select]