PAR, while a fine and handy tool, does not compile perl code (as I understand it). It simply bundles your script with the modules that it needs, along with a perl runtime, into an executable.

While that difference could be considered somewhat pedantic, consider the original poster's query. The observation was made that perl always reparses and recompiles on each invocation. PAR does not avoid that. In fact it adds another layer to it, since your code, and the included modules, are kept in a zip (-like?) format, and everything needs to be decompressed before parsing and compiling. I routinely use ActiveState's perlapp, and it does produce an executable that's often much faster than those produced by PAR, but I don't know if it's doing any parsing or compiling before emitting the exe.

Perhaps, the shift to Parrot with make this easier. I'm guessing it will be easier under parrot to snag byte code out of mid air and put it into a file, than it is under the current internals, but that remains to be seen.