Date: Tue, 31 Mar 2020 16:01:23 -0400 From: Steve Wills <swills@FreeBSD.org> To: Warner Losh <imp@bsdimp.com>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Time to svn rm include/malloc.h Message-ID: <6dbfb7cd-b4c8-dea8-8fc5-43e2b89e352d@FreeBSD.org> In-Reply-To: <CANCZdfr19HgeMLc=XwZPCGecSV0pwMw52SrbgXnKYO9vAHfLyg@mail.gmail.com> References: <CANCZdfr19HgeMLc=XwZPCGecSV0pwMw52SrbgXnKYO9vAHfLyg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yeah, a lot of ports have things like: sed -e 's/malloc.h/stdlib.h/' *.[ch] because they have autotools that check for malloc.h existence and include it if it exists, so you end up with things like: ... #include <stdlib.h> ... #if HAVE_MALLOC_H #include <stdlib.h> #endif ... which ends up harmless, but sub-optimal. Steve On 3/31/20 3:50 PM, Warner Losh wrote: > We started warning in 1994 that malloc.h was an obsolete relic of a bygon > era. It was almost removed from FreeBSD 2.0. It's time to remove it because > it causes more harm than good to ports these days. 25 years of advance > warning should be enough, I'd say. > > To that end, I plan on removing it from -current on April 15th. > > Is there any reason I shouldn't do this? > > Warner > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6dbfb7cd-b4c8-dea8-8fc5-43e2b89e352d>