Date: Fri, 10 Mar 2017 11:12:09 -0800 From: Ngie Cooper <yaneurabeya@gmail.com> To: Pedro Giffuni <pfg@FreeBSD.org> Cc: FreeBSD-arch list <freebsd-arch@freebsd.org> Subject: Re: reallocarray(3) and its uses Message-ID: <B037C704-7F5F-4921-9B3A-F66E9EDC175D@gmail.com> In-Reply-To: <44f542e8-920f-c6bc-7eb0-2e4dab86a5eb@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
> On Mar 10, 2017, at 09:00, Pedro Giffuni <pfg@FreeBSD.org> wrote: > > Hello; > > I wasn't a fan of bringing reallocarray(3) from OpenBSD, but since we have it, I thought I'd take a look at using it. It is rather easy to use so I went around opengrok'ing "realloc" in userland and crosschecking with OpenBSD and I got to this patch: > > https://reviews.freebsd.org/D9915 > > Current reviewers are mute: I am unsure if they are just deeply impressed and don't want to speak up or if they are simply too busy (most likely the later). There are still more uses in some utilities but I wanted to see what people think of the general idea. Hi Pedro! I'll take a look at the reviews sometime after I get back tomorrow night. My general thoughts are: if it's an application of library that needs to be portable, don't use it. If not, use it. I think it's kind of the same class of API call as reallocf. reallocf is a good extension, but it's not 100% portable. Thanks! -Ngiehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B037C704-7F5F-4921-9B3A-F66E9EDC175D>