Eric Wilhelm wrote:
# from Malcolm Nooning
# on Thursday 25 January 2007 08:30 am:
I am not seeing a difference on Windows.
A fairly large (~5MB) application was created. Just counting in my
head, comparing the same previously created application with the newly
created one, I am not seeing a difference. The initial
unbundling/execution takes about ten seconds for each. The subsequent
ones take about 3 seconds for each.
Do you have another PAR.pm somewhere? I suffered much headache on
windows yesterday until I discovered that parl was somehow embedding
the PAR.pm from the latter location in @INC. I don't know if it has to
do with how parl is built or what.
@INC = ('C:/Perl/lib', 'C:/Perl/site/lib'), and I had the hacked version
in $INC[0], which pp would see, but parl would keep looking at $INC[1]
(and also seemed to ignore $PERL5LIB.)
I finally discovered that by grepping for '^#.*/PAR\.pm' in the par temp
dir. I still don't know why. I believe I rebuilt parl since deleting
the other one, so I'm not sure if it is compiled-in or what.
--Eric
I have a PAR.pm in
C:\perl\site\lib
C:\perl\cpan\build\PAR-0.970\lib
C:\perl\site\lib\.svn\props
C:\perl\site\lib\.svn\text-base
C:\perl\site\lib\.svn\wcprops
C:\perl\site\lib\App\Packer
C:\perl\site\lib\Module\Install
C:\perl\cpan\build\PAR-Packer-0.970\inc\Module\Install
C:\perl\cpan\build\PAR-Packer-0.970\lib\App\Packer
I replaced the one in C:\perl\site\lib\App\Packer\PAR.pm with the new
one and pp would not work at all, so that rules out interference from
that paticular PAR.pm. I don't see that any of the others could interfere.
Your OS is qdos? That worked on the Intel 8086! I assume you have
upgraded your hardware since then but, wow!
I have wondered how blazingly fast the DOS variants would be on the PCs
of today. BTW: DOS means Denial Of Service to the newer folk.
