Diff for "BashFAQ/025"

Differences between revisions 1 and 8 (spanning 7 versions)

Hi all. It was great to see you and your new wheels at Thruxton on Sunday recipe Interesting posts, besides those spam... http://prepare76held-be.tripod.com/recipec2a.html theives oil recipe chief, http://usuarios.lycos.es/corolla35/recipec45.html trefethen trefethen wine, see you

CategoryCategory

-  ⇤ ← Revision 1 as of 2007-05-02 23:12:30 → 
  Size: 1376
  Editor: redondos
  Comment:
+   ← Revision 8 as of 2008-11-16 17:40:12 → ⇥
  Size: 308
  Editor: 193
  Comment: Hi all. It was great to see you and your new wheels at Thruxton on Sunday recipe Interesting posts, besides those spam... http://prepare76held-be.tripod.com/recipec2a.html theives oil recipe chief, ht
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-[[Anchor(faq25)]]
== 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:

{{{
    for last
    do
        : # nothing
    done

    echo "last argument is: $last"
}}}

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

{{{
    n=12        # This is the number of the argument we are interested in
    i=1
    for arg
    do
        if [ $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"
}}}

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
+Hi all. It was great to see you and your new wheels at Thruxton on Sunday recipe Interesting posts, besides those spam... http://prepare76held-be.tripod.com/recipec2a.html theives oil recipe chief, http://usuarios.lycos.es/corolla35/recipec45.html trefethen trefethen wine,  see you
----
CategoryCategory