Time to svn rm include/malloc.h

[Konstantin Belousov]

On Tue, Mar 31, 2020 at 04:01:23PM -0400, Steve Wills wrote:
> 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.
> 
So wouldn't it be more useful to remove warning and either include
stdlib.h or provide some parts of malloc-related defines, esp. the
non-portable bits from jemalloc ?

We are not in position to teach third-party sw developers good manners.

> 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 at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> > To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
> > 
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"