Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Quoting problem and crashes with ${(#)var}
- X-seq: zsh-workers 23194
- From: Peter Stephenson <pws@xxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Quoting problem and crashes with ${(#)var}
- Date: Mon, 26 Feb 2007 17:36:21 +0000
- In-reply-to: <070226092843.ZM10079@xxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <200702132111.l1DLB5rA003849@xxxxxxxxxxxxxxxxx> <070213234815.ZM5424@xxxxxxxxxxxxxxxxxxxxxx> <200702141016.l1EAGpKF016735@xxxxxxxxxxxxxx> <070214080347.ZM26428@xxxxxxxxxxxxxxxxxxxxxx> <20070214161951.e8219d6c.pws@xxxxxxx> <070225151543.ZM32724@xxxxxxxxxxxxxxxxxxxxxx> <200702261034.l1QAY1fs004257@xxxxxxxxxxxxxx> <070226081332.ZM9904@xxxxxxxxxxxxxxxxxxxxxx> <200702261624.l1QGOFWp007499@xxxxxxxxxxxxxx> <070226092843.ZM10079@xxxxxxxxxxxxxxxxxxxxxx>
Bart Schaefer wrote:
> On Feb 26, 4:24pm, Peter Stephenson wrote:
> }
> } (Before that nicechar() was added there couldn't be any metafied
> } characters at this point.)
>
> Is that going to cause problems in calling scopes? That is, do we need
> to avoid nicechar() here and instead copy some portion of it (or the
> equivalent) into wcs_nicechar() directly?
It shouldn't cause problems: as wcs_nicechar() is already supposed to
handle printable wide characters cleanly, the return values may already
contain metafied characters. See the end of the function where a normal
printable multibyte character is metafied. By "at this point", I meant
specifically in the branch handling of non-printable wide characters or
other parse failures.
pws
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview
Messages sorted by:
Reverse Date,
Date,
Thread,
Author