> ==> Question: will putting an eval around the call to Execute
> mitigate the problems caused by the unwanted failures to run,
> while still having the desired effect of pre-compiling those that
> run correctly?
Yes
> Also: for those that compile OK but refuse to
> run, will their compiled code still be retained by EmbPerl and
> shared by child processes?
>
Yes
> ==> Another proposed solution: calling "import" mode of Execute.
> Would calling Execute in "import" mode have the same
> code-caching benefits without actually trying to run the code on
> the page at server startup time?
No. It will only precompile the code between [$sub $] and [$ endsub $]
>
> ==> Would there be an advantage to combining the "eval" and
> "import" approaches to protect against pages with Embperl syntax
> errors clogging the server startup process?
>
I think, currently the eval method is the best one.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
