Differences between revisions 10 and 11
Revision 10 as of 2008-11-22 23:27:15
Size: 2246
Editor: GreyCat
Comment: first-line
Revision 11 as of 2011-02-17 16:32:44
Size: 2468
Editor: GreyCat
Comment: test -v (bash 4.2), etc.
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
If you need to distinguish between a variable that is ''undefined'' and one that is ''defined but empty'', then it becomes much trickier. There is no explicit shell command to test for existence of a variable, but there are some tricks that can be used. With bash, a way is to use "declare": If you need to distinguish between a variable that is ''undefined'' and one that is ''defined but empty'', then it becomes much trickier. There is no explicit shell command to test for existence of a variable (until bash 4.2), but there are some tricks that can be used. With older bash releases, one way is to use "declare":
Line 19: Line 19:
# returns 0 if $var exists, error otherwise # returns 0 if var exists, error otherwise
Line 26: Line 26:
if test "${foo+defined}" if test "${var+defined}"
Line 32: Line 32:

Bash 4.2 adds a `-v` test:

{{{
# Bash 4.2
if [[ -v var ]]; then echo "var is defined"; fi
}}}
Line 42: Line 49:

(This is much slower and uglier than simply using the `${var+defined}` expansion.)

How do I determine whether a variable is already defined? Or a function?

There are several ways to determine whether a variable is defined to have a non-empty value. Here are the most common ones, in order from most portable to least portable:

if test -n "$var"
if [ -n "$var" ]
if test "$var"
if [ "$var" ]
if [[ -n $var ]]
if [[ $var ]]

If you need to distinguish between a variable that is undefined and one that is defined but empty, then it becomes much trickier. There is no explicit shell command to test for existence of a variable (until bash 4.2), but there are some tricks that can be used. With older bash releases, one way is to use "declare":

# Bash
declare -p var >/dev/null 2>&1
# returns 0 if var exists, error otherwise

Here's another one that uses parameter expansion:

# Bourne
if test "${var+defined}"

This expansion results in nothing if foo is undefined. Therefore test returns false. If foo is defined (to either "" or something longer), the expansion returns "defined", and therefore test returns true. You could use any non-empty string in place of "defined", but readability is always nice.

Bash 4.2 adds a -v test:

# Bash 4.2
if [[ -v var ]]; then echo "var is defined"; fi

Another way is to use a SubShell which will exit with an error code if an unbound variable is used:

# bash/ksh work ... others?
if (set -u; : $UNBOUND_VAR) 2>/dev/null ; then
  echo "the variable has been set"
else
  echo "the variable has not been set"
fi

(This is much slower and uglier than simply using the ${var+defined} expansion.)

For determining whether a function with a given name is already defined, there are several answers, all of which require Bash (or at least, non-Bourne) commands:

# Bash
# These two are best:
if [[ $(declare -f foo) ]]     # it prints nothing, if undefined
if declare -f foo >/dev/null   # it also sets the exit status

# These are a little more obvious, but...
if [[ $(type foo 2>&1) = *\ is\ a\ function* ]]
if type foo >/dev/null 2>&1 && ! type -f foo >/dev/null 2>&1

A related question is, Why on earth does anyone want this? Why not just define the function already?

I don't know. I think it has something to do with reflection. But people keep asking it, so....

BashFAQ/083 (last edited 2022-11-26 06:06:57 by emanuele6)