Differences between revisions 1 and 25 (spanning 24 versions)
Revision 1 as of 2007-05-02 23:12:30
Size: 1376
Editor: redondos
Comment:
Revision 25 as of 2014-04-24 10:02:07
Size: 2092
Editor: pgas
Comment: blank line breaking toc
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Anchor(faq25)]] <<Anchor(faq25)>>
Line 3: Line 3:
Use {{{${10} }}}instead of {{{$10}}}. This works for ["BASH"] and KornShell, but not for older BourneShell implementations. Another way to access arbitrary positional parameters after $9 is to use {{{for}}}, e.g. to get the last parameter: Use {{{${10} }}}instead of {{{$10}}}. This works for [[BASH]] and KornShell, but not for older BourneShell implementations. Another way to access arbitrary positional parameters after $9 is to use {{{for}}}, e.g. to get the last parameter:
Line 6: Line 6:
    # Bourne
Line 13: Line 14:
Line 17: Line 17:
    # Bourne
Line 21: Line 22:
        if [ $i -eq $n ]         if test $i -eq $n
Line 23: Line 24:
            argn=arg             argn=$arg
Line 30: Line 31:
Line 37: Line 37:
and can be put into a helpful function:
Line 38: Line 39:
Although direct access to any positional argument is possible this way, it's hardly needed. The common way is to use {{{getopts(3)}}} to process command line options (e.g. "-l", or "-o filename"), and then use either {{{for}}} or {{{while}}} to process all arguments in turn. An explanation of how to process command line arguments is available here: http://www.shelldorado.com/goodcoding/cmdargs.html {{{
    # Bourne
    getarg() { # $1 is argno
        shift $1 && echo "$1"
    }
    arg12="`getarg 12 "$@"`"
}}}
In addition, bash and ksh93 treat the set of positional parameters as an [[BashFAQ/005|array]], and you may use [[BashFAQ/073|parameter expansion]] syntax to address those elements in a variety of ways:

{{{
    # Bash, ksh93
    for x in "${@:(-2)}" # iterate over the last 2 parameters
    for y in "${@:2}" # iterate over all parameters starting at $2
                            # which may be useful if we don't want to shift
}}}
Although direct access to any positional argument is possible this way, it's seldom needed. The common alternative is to use {{{getopts}}} to process options (e.g. "-l", or "-o filename"), and then use either {{{for}}} or {{{while}}} to process all the remaining arguments in turn. An explanation of how to process command line arguments is available in [[BashFAQ/035|FAQ #35]], and another is found at http://www.shelldorado.com/goodcoding/cmdargs.html

----
CategoryShell

How can I access positional parameters after $9?

Use ${10} instead of $10. This works for BASH and KornShell, but not for older BourneShell implementations. Another way to access arbitrary positional parameters after $9 is to use for, e.g. to get the last parameter:

    # Bourne
    for last
    do
        : # nothing
    done

    echo "last argument is: $last"

To get an argument by number, we can use a counter:

    # Bourne
    n=12        # This is the number of the argument we are interested in
    i=1
    for arg
    do
        if test $i -eq $n
        then
            argn=$arg
            break
        fi
        i=`expr $i + 1`
    done
    echo "argument number $n is: $argn"

This has the advantage of not "consuming" the arguments. If this is no problem, the shift command discards the first positional arguments:

    shift 11
    echo "the 12th argument is: $1"

and can be put into a helpful function:

    # Bourne
    getarg() { # $1 is argno
        shift $1 && echo "$1"
    }
    arg12="`getarg 12 "$@"`"

In addition, bash and ksh93 treat the set of positional parameters as an array, and you may use parameter expansion syntax to address those elements in a variety of ways:

    # Bash, ksh93
    for x in "${@:(-2)}"    # iterate over the last 2 parameters
    for y in "${@:2}"       # iterate over all parameters starting at $2
                            # which may be useful if we don't want to shift

Although direct access to any positional argument is possible this way, it's seldom needed. The common alternative is to use getopts to process options (e.g. "-l", or "-o filename"), and then use either for or while to process all the remaining arguments in turn. An explanation of how to process command line arguments is available in FAQ #35, and another is found at http://www.shelldorado.com/goodcoding/cmdargs.html


CategoryShell

BashFAQ/025 (last edited 2014-04-24 10:02:07 by pgas)