Re: bourne-sh behavior

> i was programing installation procedures based on bourne-sh, sed, awk and all
> other nice staff.
> 
> but than i run into troubles with the bourne-sh.
> 
> i found out the jsh (bourne-sh in solaris) is parsing strings in a rather
> funny way. i contacted sun and the answer was - that's the way bourne sh is
> working since ever. i hardly can believe this.
> 
> i tried my old 286 with interactive unix (1989) - but it does not work any
> more. the ega monitor is missing. i so try to figure out the behavior of the
> real bourne-sh by contacting other unix poeple.
> 
> the problem is simple: empty tokens are ignored. no other parsing algorythm in
> any library or tool like awk, sed ... behave that way. anyone who has
> experience in parsing information knows - it does not make sense because your
> loosing orientation.
> 
> i created a verry simple script testing the problem and showing the testsuite.
> if you are running any at&t or bsd ?nix like SunOS (not solaris), unixware, sgi
> or even svr4 implementation on amdahl, please copy the following script and
> send the output to oehlers@bluewin.ch. please make sure /bin/sh is a bourne-sh
> (linux is bash and not bourne).
> 
> 
>>>>>test.sh
> 
> #!/bin/sh
> LIST="a:b:c:::d:e:f"
> IFS=':'
> set $LIST
> echo "======= part system information ================
> uname -a
> ps
> file /bin/sh
> echo "======= part system information ================
> if [ $# -lt 8 ] ; then
>         echo "NOK==> found only $# token"
> else
>         echo "OK==> found all 8 token"
> fi
> <<<< test.sh
> 
thanks for help
Tom


--- GoldED/386 2.42.G0614+
 * Origin: Everything goes the bach runter ... 
 * http://escorts-at.org
 * http://hotels-db.com