That actually works, but I think it'd be arguably cleaner if you're just setting variables in your shell script to write some Perl to parse the variables out of the script. Currently you're looking at one exec to get the Perl code running. If your environment isn't already set, you're looking at exec'ing another shell, which then reads your shell script for inclusion and execs another perl. It's conceptually pretty simple, but it's going to be tricky to follow in the process tree should you need to do so sometime.

Compare that to something like this:

if ( not defined $ENV{'foo'} ) {
    # foo being some variable already set by your shell
    # script rather than a separate flag

    open ( my $se, '<', './set_env.sh' )
        or die "Can't read ./set_env.sh : $!\n";
    while ( <$se> ) {
        next unless /(\w+)=["']?(\w+)["']?/;
        # handling exotic formatting left as an exercise
        $ENV{$1} = $2;
    }
}

print "foo is $ENV{'foo'}!\n";
[download]

If you're running programs from within your shell script to set the environment rather than just setting variables, then I'd stick with what you have. Execing a few more times is a drawback, but it's a tiny one. It would be preferable to additional maintenance if your variable parser got any fancier than the one above.

I still question the use of a separate flag variable to let you know the environment is set up even when using the shell, but that's more of a personal preference. Other things to consider are whether you have any variables that need to be set prior to perl launching rather than after and whether you're using any of the variables that perl would need to have set as environment variables rather than just reading them into a Perl option hash.

This gave me the cleanest solution, I guess: perldoc perlrun

My script starts now like this:

#!/bin/sh

mydir=`dirname $0`
. $mydir/set_env.sh
exec perl -x $0 "$@"

#!perl
use strict;
use warnings;
# and so on...
[download]

Thanks to all who replied!

Update: In reply to Arge1 below and because I noticed today That I myself needed parameters to my script.

I appended "$@" to my exec above. This will append all parameters, individually quoted, to the exec command for my perl script to handle them.

lrwxrwxrwx  ...  inet_audit -> inet_audit.csh*
-rwx------  ...  inet_audit.csh*
-rwx------  ...  inet_audit.pl*
[download]

#!/usr/bin/tcsh
source /our/etc/perl5101env_script.csh
./inet_audit.pl $argv:q
[download]

I do kind of like the exec trick above, but how would I pass parameters in to the Perl script?

See above for the change. Appending "$@" passes all parameters unchanged to the perl script.

---

s$$([},&%#}/&/]+}%&{})*;#$&&s&&$^X.($'^"%]=\&(|?*{%
+.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e