Re^2: why the exe runs so slow compiled by pp in the first time

Replies are listed 'Best First'.
Re^3: why the exe runs so slow compiled by pp in the first time by chorankates (Novice) on Aug 23, 2011 at 16:02 UTC
no, pp just 'packs perl' into a self extracting executable. definitely has it's uses, but it does not turn your code into binary. run procmon or something similar to find the path that your script.exe is running from and you can see all of your code and any included modules	[reply]
Re^4: why the exe runs so slow compiled by pp in the first time by Achilles_Sea (Novice) on Aug 24, 2011 at 10:40 UTC
I used the procmon to find out what happened in the first run. it turns out to be what you've said, the executable really unpacked many .pm modules into the temporary directories. thanks for help	[reply]
Re^3: why the exe runs so slow compiled by pp in the first time by CountZero (Bishop) on Aug 23, 2011 at 18:07 UTC
it's disappointing Why is that disappointing? It is still Perl. And as you remarked, its main use is to deploy applications on machines that do not have Perl installed. The docs of `pp` clearly state "Source files are compressed verbatim without compilation". CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply] [d/l]
Re^4: why the exe runs so slow compiled by pp in the first time by Achilles_Sea (Novice) on Aug 24, 2011 at 10:42 UTC
thanks for reply. I will read the doc of pp :)	[reply]