From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: berrange@redhat.com
Subject: Re: [PATCH 4/8] xalloc: new function xreallocarray
Date: Thu, 22 Apr 2021 12:39:23 -0700 [thread overview]
Message-ID: <52a24d4e-b21c-f679-9502-0078595d65ad@cs.ucla.edu> (raw)
In-Reply-To: <4476169.4xcVmrf7pp@omega>
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
On 4/21/21 5:18 PM, Bruno Haible wrote:
> I disagree that xnmalloc should be deprecated.
I agree. That was a thinko in my ChangeLog entry; I meant to write
"xnrealloc". Sorry about that. I installed the attached.
[-- Attachment #2: 0001-ChangeLog-Fix-thinko.patch --]
[-- Type: text/x-patch, Size: 818 bytes --]
From ca883666cb34922d9ab1bd0ac0101970c7aa3910 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 22 Apr 2021 12:35:57 -0700
Subject: [PATCH] * ChangeLog: Fix thinko.
---
ChangeLog | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index eacc4a53f..ec81fe4b0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -116,7 +116,7 @@
When optimizing, simply use ptrdiff_t instead of xalloc_count_t.
xalloc: new function xreallocarray
- This effectively replaces xnmalloc, which perhaps should be deprecated.
+ This is the same as xnrealloc, which perhaps should be deprecated.
The name xreallocarray should be easier to remember now that
reallocarray is a standard GNU function.
* lib/xalloc.h [GNULIB_XALLOC]: Do not include xalloc-oversized.h.
--
2.27.0
next prev parent reply other threads:[~2021-04-22 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 4:01 [PATCH 1/8] safe-alloc: improve doc Paul Eggert
2021-04-19 4:01 ` [PATCH 2/8] backupfile: simplify via realloc-gnu Paul Eggert
2021-04-19 4:01 ` [PATCH 3/8] group-member: " Paul Eggert
2021-04-19 4:01 ` [PATCH 4/8] xalloc: new function xreallocarray Paul Eggert
2021-04-22 0:18 ` Bruno Haible
2021-04-22 19:39 ` Paul Eggert [this message]
2021-10-19 23:49 ` Paul Eggert
2021-04-19 4:01 ` [PATCH 5/8] xalloc-oversized: fix SIZE_MAX optimization bug Paul Eggert
2021-04-19 4:01 ` [PATCH 6/8] safe-alloc: simplify via reallocarray Paul Eggert
2021-04-19 4:01 ` [PATCH 7/8] calloc-gnu: now LGPLv2+ Paul Eggert
2021-04-19 4:01 ` [PATCH 8/8] safe-alloc: fix pointer implementation Paul Eggert
2021-04-22 18:20 ` [PATCH 1/8] safe-alloc: improve doc Eric Blake
2021-04-22 19:32 ` Paul Eggert
2021-04-22 19:43 ` Eric Blake
2021-04-22 20:27 ` Eric Blake
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52a24d4e-b21c-f679-9502-0078595d65ad@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=berrange@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).