This question already has an answer here:
It seems to me that they both store all the command-line arguments.
So is there a difference between the two?
This question already has an answer here:
It seems to me that they both store all the command-line arguments.
So is there a difference between the two?
A key difference from my POV is that
"$@"
preserves the original number of arguments. It's the only form that does.For example, if file my_script contains:
and I run it like this:
I will get this output:
The difference is subtle;
"$*"
creates one argument separated by the$IFS
variable, while"$@"
will expand into separate arguments. As an example, consider:When run with multiple arguments:
For more details:
http://www.gnu.org/software/bash/manual/bashref.html#Special-Parameters
$*
Expands to the positional parameters, starting from one. When the expansion occurs within double quotes, it expands to a single word with the value of each parameter separated by the first character of the IFS special variable. That is, "$*" is equivalent to "$1c$2c...", where c is the first character of the value of the IFS variable. If IFS is unset, the parameters are separated by spaces. If IFS is null, the parameters are joined without intervening separators.
$@
Expands to the positional parameters, starting from one. When the expansion occurs within double quotes, each parameter expands to a separate word. That is, "$@" is equivalent to "$1" "$2" .... If the double-quoted expansion occurs within a word, the expansion of the first parameter is joined with the beginning part of the original word, and the expansion of the last parameter is joined with the last part of the original word. When there are no positional parameters, "$@" and $@ expand to nothing (i.e., they are removed).