From owner-freebsd-hackers Sun Mar 5 20:30:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 15C8A37BC32 for ; Sun, 5 Mar 2000 20:30:20 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id UAA27587; Sun, 5 Mar 2000 20:30:19 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id UAA85900; Sun, 5 Mar 2000 20:30:18 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 5 Mar 2000 20:30:18 -0800 (PST) Message-Id: <200003060430.UAA85900@vashon.polstra.com> To: Doug@gorean.org Subject: Re: empty lists in for In-Reply-To: <38C2B805.EA899C32@gorean.org> References: <57223.952177003@axl.ops.uunet.co.za> <20000305093539F.jhix@mindspring.com> <38C2B805.EA899C32@gorean.org> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38C2B805.EA899C32@gorean.org>, Doug Barton 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