From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <borsenkow.msk@sni.de>,
"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Possible bug with ${(A)foo=} and ${(AA)foo=}
Date: Tue, 22 Jun 1999 17:36:28 +0000 [thread overview]
Message-ID: <990622173628.ZM30363@candle.brasslantern.com> (raw)
In-Reply-To: <007a01bebcca$33379950$21c9ca95@mow.siemens.ru>
On Jun 22, 8:13pm, Andrej Borsenkow wrote:
} Subject: Possible bug with ${(A)foo=} and ${(AA)foo=}
}
} While playing with something else I discovered, that it is impossible to
} create empty array with this form and it is impossible to create hash in
} this way without error message:
The first problem is what causes the second, though creating an empty AA
this way would create an empty hash table (normally the hash table is not
created until the AA has at least one value).
} I think, that if ${foo=} is valid at all, then we must distinguish between
} no value and empty value.
I've been looking at this ... we can distinguish between ${x=} and ${x=''},
but without jumping through a lot of hoops we can't distinguish whether $y
is set or unset in ${x=$y}. Perhaps that doesn't matter ...
Anyway, I've just run out of time to work on this, so a patch will have to
wait unless someone else gets to it.
} It is the same as in command line (and, after all, we
} compute it using the same rules?)
I'm not sure what you mean by that, but we don't parse it with the same
code.
} [Background - ${(AA)foo=} seems currently to be the only way to create
} global hash from within Zsh function]
Hmm, yes, that does seem to be an issue.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-06-22 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 16:13 Andrej Borsenkow
1999-06-22 17:36 ` Bart Schaefer [this message]
1999-06-23 10:02 ` Peter Stephenson
1999-06-24 15:36 ` PATCH: " Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=990622173628.ZM30363@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=borsenkow.msk@sni.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).