From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10932 invoked by alias); 3 Dec 2016 19:57:16 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40075 Received: (qmail 24774 invoked from network); 3 Dec 2016 19:57:15 -0000 X-Qmail-Scanner-Diagnostics: from know-smtprelay-omc-11.server.virginmedia.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(80.0.253.75):SA:0(-0.0/5.0):. Processed in 1.120595 secs); 03 Dec 2016 19:57:15 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.w.stephenson@ntlworld.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _smtprelay.virginmedia.com designates 80.0.253.75 as permitted sender) X-Originating-IP: [86.21.219.59] X-Spam: 0 X-Authority: v=2.1 cv=ZKcq4iPb c=1 sm=1 tr=0 a=utowdAHh8RITBM/6U1BPxA==:117 a=utowdAHh8RITBM/6U1BPxA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=Q1Uj5y2PNnht3CVl8_oA:9 a=CjuIK1q_8ugA:10 a=GNzdORjivnkA:10 a=z9dJwno5l634igLiVhy-:22 Date: Sat, 3 Dec 2016 19:57:03 +0000 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: The -~ bug Message-ID: <20161203195703.03eb1fc9@ntlworld.com> In-Reply-To: <161202163730.ZM2895@torch.brasslantern.com> References: <161202163730.ZM2895@torch.brasslantern.com> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 2 Dec 2016 16:37:30 -0800 Bart Schaefer wrote: > Is it safe to do the following, which changes the string passed in via > *namptr? Or is it necessary to dupstring()? Thanks, I think that's fine --- this always (unless there's a path I've forgotten about) comes from parsed command line argument which are all off the heap. pws