in reply to the -x command line parameter

Another useful and actual real world example is <Perl></Perl> sections in the Apache httpd.conf file. You can simply do:
randomApacheVar = 1 var2=3 <Perl> #!perl my $perl = 'code'; some('more','code'); #etc __END__ </Perl>
And easily check if it compiles, or even what it does by doing perl -x httpd.conf

Replies are listed 'Best First'.
Re^2: the -x command line parameter
by tilly (Archbishop) on Aug 09, 2004 at 05:16 UTC
    You can do even better than that. I've seen the above technique used to create synchronized httpd.conf files, so that information that in one is maintained through mod_perl in the next has the Perl expanded out so that it can be used with a non-mod_perl Apache server. (This for a reverse proxy config, the non-mod_perl server handles all of the static requests and forwards what it needs to to the mod_perl servers.)
      could you elaborate on "so that information that in one is maintained through mod_perl in the next has the Perl expanded out "? thanks