RE: POE::Component::Resolver patch for PAR compatibility

Hi Steffen,

an "easier way" could mean some means to minimize the startup costs for the other Perl scripts -
as --reuse targets toward the execution of external Perl scripts, we are talking here about "internal" scripts,
in our case a one- or two-liner packed into the archive since -e "....->main()" is not an option with PAR.
So the question is if given all that knowledge from within PAR execution, if there is a faster way than the
externally usable --reuse option.

Best regards,
	Markus

-----Original Message-----
From: Steffen Mueller [mailto:[email protected]] 
Sent: Thursday, May 19, 2011 10:43 PM
To: Markus Jansen
Cc: [email protected]; [email protected]
Subject: Re: POE::Component::Resolver patch for PAR compatibility

Hi Markus,

On 05/19/2011 10:35 AM, Markus Jansen wrote:
> Steffen and Roderich: could you please scrutinize my patch from a PAR 
> perspective? I know that I have been a little bit more paranoid than 
> necessary when trying to detect whether a) the script runs under PAR, 
> and b) the "external Perl" version is wanted. Regarding the calling 
> via --reuse - is there an easier/faster way?

Keep in mind --reuse is a little bit experimental and has likely not been tested a huge lot. Worked for me, though.

Regarding "paranoia", I think it's important to take care. Executing stuff from an environment variable...

What would you suggest as an easier way?

Best regards,
Steffen