#one of the intermediate mails in this thread was accidentally not send to
the list. the question was how to
#discriminate between a variable set to null and an unset variable,
specifically if IFS is concerned.
On Thu, 20 Jun 2013 03:01:39 +0200, David Korn <[email protected]>
wrote:
Subject: Re: Re: [ast-users] ksh93: IFS question
--------
You can use
[[ ${x+abc} ]] || print x is unset
yes, but this does not work for IFS. any chance here? of course I don't
want to argue against the standard (silently use default value if IFS
unset), but at least the combination of "if IFS is unset, use default IFS
value" & "after unset, IFS content is printed/reported and treated (by the
above construct, e.g.) as null (which -- if this were the real value of
IFS -- would switch off field splitting completely) seems inconsistent to
me: either it should really be detectable by the above construct ("IFS is
really unset and the handling of this case (use default value for
splitting) is explained in the standard") or an unset attempt on IFS
should explicitly set it to the default (I think the latter is not really
possible/against standard, but the former should be?).
or am I wrong?
joerg
David Korn
[email protected]
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
ast-users mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-users
