What if they are set up during the script's startup and then stay constant? Then they were changed (well defined) once during one of the several "runtimes" but still they are constant for the rest of the script and may even be treated as constants by the optimizer. If it's done right.
For example:
BEGIN {
# set "Constants" equal to first three command line arguments
eval <<EOF;
sub ARG1{"$ARGV[0]"}
sub ARG2{"$ARGV[1]"}
sub ARG3{"$ARGV[2]"}
EOF
}You have to do your setup runtime time before the code to be optimized is seen even once.
-- [EMAIL PROTECTED] Include phrase "cat and buttered toast" to get through my filter
