Date: Sun, 5 Mar 2000 20:30:18 -0800 (PST) From: John Polstra <jdp@polstra.com> To: Doug@gorean.org Cc: hackers@freebsd.org Subject: Re: empty lists in for Message-ID: <200003060430.UAA85900@vashon.polstra.com> In-Reply-To: <38C2B805.EA899C32@gorean.org> References: <Pine.BSF.4.21.0002212205230.36736-100000@iclub.nsu.ru> <57223.952177003@axl.ops.uunet.co.za> <20000305093539F.jhix@mindspring.com> <38C2B805.EA899C32@gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <38C2B805.EA899C32@gorean.org>,
Doug Barton <Doug@gorean.org> wrote:
>
> Given that Bash in both standard and POSIX mode complains about 'for i
> in ; do echo $i; done', I would say that it's not POSIX compatible. What
> could/does depend on this behavior "working?"
It works for the realistic cases that might actually be useful. E.g.,:
x=
for i in $x; do
echo $i
done
works fine. I don't think it matters very much that the pathological
case "for i in ; ..." doesn't work.
John
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003060430.UAA85900>