Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!petunia!news
From: barb@library.calpoly.edu (Barbara Nash)
Newsgroups: comp.unix.questions
Subject: Re: Bourne shell syntax problem?
Message-ID: <280fa180.65b8@petunia.CalPoly.EDU>
Date: 20 Apr 91 02:03:44 GMT
Distribution: usa
Organization: Computer Services - Kennedy Library, Cal Poly SLO
Lines: 46


croten@ltpsun.gsfc.nasa.gov (Charles D. Roten) says.......
>
>    I am having trouble getting a Bourne shell to run, and have come to
>suspect that the problem is in the section where I parse the variables.
>The script is rather long (~260 lines) so I will only include the suspect
>portion.
>
>-------------------- script follows --------------------
>#!/bin/sh
>
> [comments deleted]
>
[lotsa stuff deleted for brevity's sake]
>
># Now, parse the rest of the arguments, for cases where there are 1 or more
>#    arguments.
>
>for i in $*; do
>   case $i in
[lotsa case stuff deleted for more brevity]
>      *)    if test "$data" = ""; then
>               data=$i
>            elif test "$normal = ""; then
                       ^^^^^^^^^^^^^
                       You've only got three quotes here, you need another
                       after the "$normal.  This is prolly why you are getting
                       the unexpected EOF error.
>
>    I would greatly appreciate an explanation of the the nature of the 
>goof.  Thanks in advance.

Sure, no problem.  Forgetting a quote mark seems to be my favorite shell
proggin' error as well!  =-) =-)


Good luck,
Barb



-- 
--------------------------------------------------------------------------------
Barbara Nash, Asst. SysAdmin                       barb@library.calpoly.edu
Kennedy Library Computer Services                  bnash@polyslo.calpoly.edu
Disclaimer:  My opinions are my own, the library has enough without taking mine.