Returning Values from Bash Functions
Bash functions, unlike functions in most programming languages do not allow you to return a value to the caller. When a bash function ends its return value is its status: zero for success, non-zero for failure. To return values, you can set a global variable with the result, or use command substitution, or you can pass in the name of a variable to use as the result variable. The examples below describe these different mechanisms.
Although bash has a return statement, the only thing you can specify with it is the function's status, which is a numeric value like the value specified in an exit statement. The status value is stored in the $? variable. If a function does not contain a return statement, its status is set based on the status of the last statement executed in the function. To actually return arbitrary values to the caller you must use other mechanisms.
The simplest way to return a value from a bash function is to just set a global variable to the result. Since all variables in bash are global by default this is easy:
function myfunc()
{
myresult='some value'
}
myfunc
echo $myresult
The code above sets the global variable myresult to the function result. Reasonably simple, but as we all know, using global variables, particularly in large programs, can lead to difficult to find bugs.
A better approach is to use local variables in your functions. The problem then becomes how do you get the result to the caller. One mechanism is to use command substitution:
function myfunc()
{
local myresult='some value'
echo "$myresult"
}
result=$(myfunc) # or result=`myfunc`
echo $result
Here the result is output to the stdout and the caller uses command substitution to capture the value in a variable. The variable can then be used as needed.
The other way to return a value is to write your function so that it accepts a variable name as part of its command line and then set that variable to the result of the function:
function myfunc()
{
local __resultvar=$1
local myresult='some value'
eval $__resultvar="'$myresult'"
}
myfunc result
echo $result
Since we have the name of the variable to set stored in a variable, we can't set the variable directly, we have to use eval to actually do the setting. The eval statement basically tells bash to interpret the line twice, the first interpretation above results in the string result='some value' which is then interpreted once more and ends up setting the caller's variable.
When you store the name of the variable passed on the command line, make sure you store it in a local variable with a name that won't be (unlikely to be) used by the caller (which is why I used __resultvar rather than just resultvar). If you don't, and the caller happens to choose the same name for their result variable as you use for storing the name, the result variable will not get set. For example, the following does not work:
function myfunc()
{
local result=$1
local myresult='some value'
eval $result="'$myresult'"
}
myfunc result
echo $result
The reason it doesn't work is because when eval does the second interpretation and evaluates result='some value', result is now a local variable in the function, and so it gets set rather than setting the caller's result variable.
For more flexibility, you may want to write your functions so that they combine both result variables and command substitution:
function myfunc()
{
local __resultvar=$1
local myresult='some value'
if [[ "$__resultvar" ]]; then
eval $__resultvar="'$myresult'"
else
echo "$myresult"
fi
}
myfunc result
echo $result
result2=$(myfunc)
echo $result2
Here, if no variable name is passed to the function, the value is output to the standard output.
Mitch Frazier is an Associate Editor for Linux Journal.
Trending Topics
| You Need A Budget | Feb 10, 2012 |
| The Linux powered LAN Gaming House | Feb 08, 2012 |
| Creating a vDSO: the Colonel's Other Chicken | Feb 06, 2012 |
| Your CMS Is Not Your Web Site | Feb 01, 2012 |
| Casper, the Friendly (and Persistent) Ghost | Jan 31, 2012 |
| Razor-qt 0.4 - Qt based Desktop Environment | Jan 30, 2012 |
- This is a great program. We
2 hours 32 min ago - No Air for Linux
4 hours 22 min ago - HEWLETT PACKARD created
4 hours 32 min ago - HEWLETT PACKARD created
4 hours 34 min ago - very helpful :)
4 hours 56 min ago - I'll give it a whirl
13 hours 30 min ago - TFPT, don't you mean TFTP!? I
21 hours 59 min ago - wunderbar!!
22 hours 17 min ago - Lubuntu on a USB key
1 day 12 hours ago - Because XFCE is neither fish
2 days 3 hours ago





Comments
Bash can return integer values from functions
If you only want to return an integer value from a bash function, the will work:
#!/bin/bash
function return_code_test ()
{
return 50
}
return_code_test
echo "return_code_test returned $?"
some thoughts on returning variables
The difference in speed between assignment and eval is possibly not significant, but the difference between either and fork is large. If you're calling a function thousands of times, the fork method "myvar=$(myfunc())" will be much slower.
I write most of my bash functions to simply set the ${_RET} variable.
some thoughts on returning variables
for control the result in a function, i use "echo" as return value.
In this way i can call the function in any script position and verify the result.
-----------------------------
#!/bin/bash
cmdPing=`which ping`
pingThis="qqqperl.com"
ckping(){
xpingThis=`$cmdPing -c1 $pingThis &>/dev/null`
if [ $? == 0 ];then
echo "true"
return 10
else
echo "false"
return 20
fi
}
ckping
echo "$? this is the return of the function"
echo "############################"
echo "$? this is the echo return"
echo -e "
-------------------------
now call the function"
if [[ "$(ckping)" == "true" ]];then
echo -e "
\t $pingThis ok
"
#wget -N $pingThis/myDownload
else
echo -e "
\t $pingThis no pong
"
fi
echo "-------------------------"
sorry for my poor English
ciao Mario