From: Peter Stephenson <pws@csr.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: caps strings
Date: Tue, 03 Mar 2009 18:31:00 +0000 [thread overview]
Message-ID: <200903031831.n23IV0QM028011@news01.csr.com> (raw)
In-Reply-To: <237967ef0903031021yf6632adhd399c06289ff6ddc@mail.gmail.com>
Mikael Magnusson wrote:
> Does dupstring somehow allocate from the stack?
Yes.
> Should I use it
> instead of re-metafy()ing in attr.c too, or maybe it doesn't really
> matter which you do?
It's not crucial; dupstring() is probably slightly neater.
pws
prev parent reply other threads:[~2009-03-03 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 17:43 Peter Stephenson
2009-03-03 17:55 ` Mikael Magnusson
2009-03-03 18:00 ` Mikael Magnusson
2009-03-03 18:10 ` Peter Stephenson
2009-03-03 18:21 ` Mikael Magnusson
2009-03-03 18:31 ` Peter Stephenson [this message]
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=200903031831.n23IV0QM028011@news01.csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.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).