Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!telxon!gorpong
From: gorpong@telxon.uucp (Gordon C. Galligher)
Newsgroups: gnu.bash.bug
Subject: Re: BASH 1.0.4 Bug (maybe)
Keywords: bash, 1.04, bug, SunOS 4.0.3, Sun 4/280
Message-ID: <476@telxon.UUCP>
Date: 28 Feb 90 16:21:09 GMT
References: <474@telxon.UUCP>
Sender: news@telxon.UUCP
Reply-To: gorpong@telxon.UUCP (Gordon C. Galligher)
Distribution: gnu
Organization: Telxon Corporation, Akron Ohio (NNTP with a :-)
Lines: 36

My apologies.  I have the following:

In article <474@telxon.UUCP> gorpong@telxon (Gordon C. Galligher) writes:

>
>	bash$ for i in this is a test
>	> do
>	> echo I == $i
>	> done
>	>
> .......^

Actually, EVEN if I try:

	bash$ for i in this is a test ; do echo I == $i ; done
	bash>
and
	bash$ for i in this is a test ;
	bash> do
	bash> echo I == $i
	bash> done
	bash>

So you see, no matter what way of legal, and illegal syntax, it still
doesn't work.  Actually, the for followed by return-followed by do, should
be considered legal syntax (at least in Bourne Shell), and it doesn't
require the use of the ';' as I was told in a mail message.

Therefore, I still feel this is a bug.  Thanks.

		-- Gordon.

Gordon C. Galligher  <|> ..!uunet!telxon!gorpong <|> telxon!gorpong@uunet.uu.net
Telxon Corporation   <|> "I am attempting, ma'am, to make a mnemonic memory
Akron, Ohio, 44313   <|> circuit out of stone knives and bearskins"  - Spock
(216) 867-3700 (3512)<|>	_City on the Edge of Forever_