This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Why was the reallocarray function not added to glibc?
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Dennis Wölfing <denniswoelfing at gmx dot de>, <libc-alpha at sourceware dot org>
- Cc: <nd at arm dot com>
- Date: Mon, 3 Apr 2017 16:49:11 +0100
- Subject: Re: Why was the reallocarray function not added to glibc?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: arm.com; dkim=none (message not signed) header.d=none;arm.com; dmarc=none action=none header.from=arm.com;
- Nodisclaimer: True
- References: <d3ddd2fb-7f6c-3a85-5c00-666200275997@gmx.de>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 03/04/17 16:21, Dennis Wölfing wrote:
> The reallocarray function is a useful function that originates from OpenBSD and
> that checks for overflow when (re)allocating memory. I saw in the mail archives
> that a patch that implements reallocarray was already contributed in May 2014.
>
> Here is the link: https://sourceware.org/ml/libc-alpha/2014-05/msg00481.html
>
> However this patch was never applied even though I could not find any real
> objections in the mail archives.
it violates iso c and posix namespace rules
https://sourceware.org/ml/libc-alpha/2014-05/msg00506.html
>
> Is there any reason to not add reallocarray to glibc? If not, should the patch
> linked above be applied?
>
> Dennis Wölfing
>