Terry Lambert wrote:
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.)If a legacy application stops working because a system changes, it's the fault of the system doing the changing, not the fault of the people back in 1984 who didn't know ANSI was going to bung-up the C language until their application no longer worked.There has to be some allowance for the continuity of code; it can't just be orphaned instantaneously, without some warning from the system vendor.
Okay, it's only a small thing, but if you have too many of these small things to deal with at once, you're in porting Hell. ;)
Keith
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
