From mboxrd@z Thu Jan 1 00:00:00 1970 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes From: "Bart Schaefer" Message-Id: <990129222217.ZM10257@candle.brasslantern.com> Date: Fri, 29 Jan 1999 22:22:17 -0800 In-Reply-To: <19990128175016.A24442@fysh.org> Comments: In reply to Phil Pennock "Re: set -A and stat -A vs. typeset -A and stat -H" (Jan 28, 5:50pm) References: <990128014724.ZM32736@candle.brasslantern.com> <19990128132316.B19607@fysh.org> <990128093329.ZM1677@candle.brasslantern.com> <19990128175016.A24442@fysh.org> X-Mailer: Z-Mail (4.0b.820 20aug96) To: zsh-workers@sunsite.auc.dk Subject: Re: set -A and stat -A vs. typeset -A and stat -H MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailing-List: 5116 On Jan 28, 5:50pm, Phil Pennock wrote: } Subject: Re: set -A and stat -A vs. typeset -A and stat -H } } Generally, I have no objections whatsoever to changing [stat -H]. I } was just gratified to see someone modify the examples to make use of my } addition. A nice warm fuzzy feeling inside... :^) Here's an idea ... simply use `stat -A' for both, and have stat examine the type of the parameter to which it's assigning to choose the behavior. For that to work cleanly, though, stat would have to refuse to create a parameter that didn't already exist. `set -A' could do the same, for that matter, though it's been around a lot longer so it probably couldn't get away with refusing to create new parameters. } Erm, Bart, is that the first time that you've used a smiley on the } zsh-workers list? :^) *ducks* No, it isn't the first time, but a while back someone I worked with used smileys so often that they became meaningless/annoying to everyone else, and consequently I pretty much stopped using them unless my meaning might be completely misconstrued without one. } Anyway, back on topic. Given all this overloading in typeset and set, } how feasible is it to do a split-out, similar to the completion stuff } recently? One can do almost anything with modules, except modify the lexer/parser. } Ie, carefully examine the functionality requirements, add (I } suspect) three new builtins, organise the options consistenly for those. What three are you thinking of? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com