From: Oliver Kiddle <opk@zsh.org>
To: zsh-workers@zsh.org
Subject: Re: [PATCH 3/3] autoconf: prepare for 2.70
Date: Fri, 09 Apr 2021 22:08:36 +0200 [thread overview]
Message-ID: <82651-1617998916.051731@a6Dr.Jrvx.lcPg> (raw)
In-Reply-To: <6C8E81D3-E859-4C65-97D0-90E614816619@kba.biglobe.ne.jp>
Jun T wrote:
> I also tested on a few systems and fund no problems.
Good. I've now applied them.
> I think mem.c can be further simplified as follows (discard unnecessary macros):
Yes, that does simplify it somewhat. No objections from me. But I'll
leave you to commit it.
> Are there any systems that still require --enable-zsh-mem?
I don't think I ever have needed it especially. I don't know if anyone
perhaps finds it useful for debug capabilities though some of the common
malloc implementations probably have better functionality for that
anyway. Cutting away some of this old stuff from the zsh code base may
make it easier to maintain. So again, no objections from me but in this
case there may be others with an interest in keeping it.
Oliver
next prev parent reply other threads:[~2021-04-09 20:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 5:41 [PATCH 0/3] Build fixes Felipe Contreras
2020-12-31 5:41 ` [PATCH 1/3] src: fix build warnings Felipe Contreras
2021-01-02 11:22 ` Daniel Shahaf
2021-01-02 16:41 ` Mikael Magnusson
2021-01-02 18:30 ` Felipe Contreras
2021-01-04 5:14 ` Daniel Shahaf
2021-03-27 19:28 ` Lawrence Velázquez
2021-04-04 6:38 ` Jun. T
2020-12-31 5:41 ` [PATCH 2/3] autoconf: remove deprecated functions Felipe Contreras
2021-03-27 19:37 ` Lawrence Velázquez
2021-04-03 15:04 ` Lawrence Velázquez
2020-12-31 5:41 ` [PATCH 3/3] autoconf: prepare for 2.70 Felipe Contreras
2021-03-27 19:38 ` Lawrence Velázquez
2021-04-03 15:44 ` Lawrence Velázquez
2021-04-08 22:44 ` Oliver Kiddle
2021-04-09 4:18 ` Jun T
2021-04-09 20:08 ` Oliver Kiddle [this message]
2021-04-09 20:28 ` Peter Stephenson
2021-04-09 23:04 ` Bart Schaefer
2021-04-09 23:19 ` Mikael Magnusson
2021-04-10 0:37 ` Jun. T
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=82651-1617998916.051731@a6Dr.Jrvx.lcPg \
--to=opk@zsh.org \
--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).