In the last episode (Jan 14), Keith Jones said:
> I'm new to this list, so apologies if this has been stated before,
> but having just discovered that /usr/include/malloc.h has gone from
> being merely deprecated (in -STABLE) to obsolete (in -RC), I'm with
> Terry on this one. Yes it may be the right thing to do from a
> standards point of view, but there's still a lot of legacy code out
> there that uses it. (And a lot of new code too, I'll bet, since
> malloc.h still works fine and dandy on Linux, and despite the fact
> that the man page has said '#include <stdlib.h>' for a few years now,
> developers still fail to RTFM, it appears.)
revision 1.2
date: 1994/11/17 11:04:49; author: ache; state: Exp; lines: +4 -15
branches: 1.2.6;
By Bruce and Joerg suggestions and by looking into June version
of NetBSD simple #include <stdlib.h> into malloc.h
Put #warning that this file is obsoleted ( by Joerg suggestion)
I think 8 years of warnings is more than enough :) Out of the ~7100
ports built by the package building cluster on -current, only the sdcc
port is currently broken because of malloc.h. I have no data on how
many ports patch the source to remove references to it, though. A much
bigger problem when going to -current is the gcc 2.95 -> 3.2 upgrade;
lots of c++ programs break because things have moved out of the global
namespace into std::
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
