My problem:
#!/bin/bash
function testFunc(){
echo "param #1 is :" $1
echo "param #2 is :" $2
}
param1="param1"
param2="param2"
testFunc $param1 $param2
This way the output is:
param #1 is : param1
param #2 is : param2
But when I set param1 to empty string:
param1=""
Then the output is the following:
param #1 is : param2
param #2 is :
I guess the problem is that when the first parameter is empty, it's not declared, so it actually doesn't get passed as a function parameter.
If that is the problem, then is there a way to declare a variable "empty string" in bash, or is there any workaround to get the expected behavior?
Note: It works as expected if I call the function like this:
testFunct "" $param2
But I want to keep the code clean.
UPDATE:
I recently discovered the -u
flag which raises an error in case an unbound variable is about to be used.
$ bash -u test.sh
param #1 is : param1
test.sh: line 5: $2: unbound variable
On the first case you call the script with
testFunct param2
. Hence, it understandsparam2
as the first parameter.It is always recommendable to pass parameters within quotes to avoid this (and to be honest, for me it is cleaner this way). So you can call it
So to pass an empty variable you say:
See an example:
Given this function:
Let's call it in different ways:
Another best practice is to check the number of parameters passed using $#.
However, this does not solve the problem of one empty parameter, how would you know if the param1 is empty or param2 is empty. Therefore both checks are good parctices.