From: Bart Schaefer <schaefer@brasslantern.com>
To: James <tirtajames45@gmail.com>
Cc: Oliver Kiddle <opk@zsh.org>, zsh-workers@zsh.org
Subject: Re: [PATCH v2] prefer memcpy() over strcpy()
Date: Mon, 25 Mar 2024 19:26:45 -0700 [thread overview]
Message-ID: <CAH+w=7ZrB5r3k7WsOWqGH_QQ72Tiqu+LGKQUXuzoq9CRYfXd9A@mail.gmail.com> (raw)
In-Reply-To: <CANDqPp35KYKZT7QkNjyVfoEtwG7gn8bJDQHfcRSfTCD6nea58g@mail.gmail.com>
On Mon, Mar 25, 2024 at 7:18 PM James <tirtajames45@gmail.com> wrote:
>
> I think it would be better to make it a macro for now. The function call overhead may become a pessimization for small strings.
Didn't we go over this (and have a discussion about naming the macro)
a few months ago?
next prev parent reply other threads:[~2024-03-26 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 7:11 James Tirta Halim
2024-03-26 0:42 ` Oliver Kiddle
2024-03-26 2:18 ` James
2024-03-26 2:26 ` Bart Schaefer [this message]
2024-03-26 2:33 ` James
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='CAH+w=7ZrB5r3k7WsOWqGH_QQ72Tiqu+LGKQUXuzoq9CRYfXd9A@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=opk@zsh.org \
--cc=tirtajames45@gmail.com \
--cc=zsh-workers@zsh.org \
/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).