(I suddenly don't remember if $* is the correct name for all parameters, but some of the other guys on the list should know.)
Indeed it is. :)
cough cough sputter... If you don't know why you use "$@" instead of $* make sure you don't work on anything security-related or mission-critical. Sorry if it sounds arrogant, but I'm getting a bit tired of explaining it. Read the bash man page about parsing, quoting and variable expansion. Volker
Ok, the difference I found after reading the manpage was when using double quotes around it. "$*" seems to become one "string", while with "$@" you have it still split. Is this the whole point? Can someone who is not tired explain to me what the importance is for security? (I'd rather know it before I work on anything mission critical.) thanks,
From Volker Kuhlmann to suse-linux-e@suse.com about Re: [SLE] suse 7.2!!:
If you don't know why you use "$@" instead of $* make sure you don't work on anything security-related or mission-critical.
Sorry if it sounds arrogant, but I'm getting a bit tired of explaining it. That's ok. I'm used to arrogance. Read the bash man page about parsing, quoting and variable expansion.
Volker
-- dieter
participants (2)
-
dieter -
Volker Kuhlmann