I have a function like this
function test(){
local param1=${1}
local param2=${2}
echo "Hey ${param1} ${param2}"
}
And then, in another part of the script I have this
echo ${command}
$(command)
echo "Completed"
The output of that execution is
test param1 param2
Completed
So, as you can see, the function test was not executed.
I was looking a way to do that if possible in my shell script.
The good practice for this is described below:
command=(test a b)
echo ${command}
"${command[@]}"
echo "Completed"
The above code will use an array to store the command and the parameters, and it will call the function appropriately.
To specifically fix the expected behavior of your code, you could call the function using ${command} or $command, which is different from $(command). But the preferred practice, and more secure way of doing that is to follow the previous suggestion.
#!/bin/bash
function test(){
local param1=${1}
local param2=${2}
echo "Hey ${param1} ${param2}"
}
command="test a b"
echo ${command}
${command}
echo "Completed"
command=( test a b ), then "${command[@]}" to run it. That way you can do things like command=( printf '%s\n' "first line" "second line" ), and "${command[@]}" correctly prints two lines. Try it yourself if you want to see what that does with the string approach; it's not pretty.
commandis a shell builtin which does nothing when called without any args (try runningcommandat the command prompt);$( command )says to run the (builtin)commandin a subshell ... which still does nothing; to reference the variablecommandtry$( $command )... not saying your code will work as expected but it should get you further along in the process; generally speaking ... naming variables, function and scripts with the same names as builtins and system executables (eg,testandcommand) isn't a recommended practicefunction test() {, see wiki.bash-hackers.org/scripting/obsolete. Modern POSIX-compliant function declaration syntax is justtest() {; 1980s ksh usedfunction test {with no(); merging the two gives you the worst of both worlds, as your code is compatible with neither legacy ksh nor baseline POSIX.testas your function name is probably best avoided, as it shadows the built-intestcommand.