From: Doug Barton <[EMAIL PROTECTED]>
> John Polstra already pointed this out, and Bash handles this like you
> would expect. There is a difference between expanding an empty list and
> trying to expand a list that isn't there.
Convince me that nothing like the following exists in the
ports framework and /usr/src and I'd be ok with a change
*after* 4.0 release (repeats himself)
# Makefile.foo
FOOVAR=
.
.
.
BARVAR=${FOOVAR}
baz:
for i in ${BARVAR} ; do \
${BLAP} $$i ; \
done
To me, changing it right now on the eve of -release
would be gratuitous. Later I would be fine with it.
I still prefer /bin/sh being able to handle an empty
literal list but would yield to the desires of others.
--
Jerry Hicks
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Re: empty lists in for Doug Barton
- Re: empty lists in for John Polstra
- Re: empty lists in for Doug Barton
- Re: empty lists in for John Polstra
- Re: empty lists in for Martin Cracauer
- Re: empty lists in for (/bin/sh) Max Khon
- Re: empty lists in for (/bin/sh... Martin Cracauer
- Re: empty lists in for W Gerald Hicks
- Re: empty lists in for W Gerald Hicks
- Re: empty lists in for Doug Barton
- Re: empty lists in for W Gerald Hicks
- Re: empty lists in for Doug Barton
- Re: empty lists in for John Polstra
- Re: empty lists in for W Gerald Hicks
- Re: empty lists in for Chris Costello
- Re: empty lists in for Max Khon
- Re: empty lists in for Chris Costello
- Re: empty lists in for David Scheidt
- Re: empty lists in for Arindum Mukerji
- Re: empty lists in for Christian Weisgerber
- Re: empty lists in for Sheldon Hearn

