Dan Nelson wrote:
I think 8 years of warnings is more than enough :)
I agree with you that it ought to be. Personally I think people that still use "#include <malloc.h>" should be forced to write out "#include <stdlib.h>" 1000 times, then eat the paper. However, it is an imperfect universe. ;)
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.
(Overkill use of perl. I'm sorry.)
[keith@athlon ports]$ find [a-c]* d[ae]* [e-x]* -type d | perl -pe 's/^(.*?\/.*?)\/.*$/$1/;' | sort -u | wc -l
7384
[keith@athlon ports]$ grep -r malloc.h [a-c]* d[ae]* [e-x]* | perl -pe 's/^(.*?\/.*?)\/.*$/$1/;' | sort -u | wc -l
342
That doesn't include the non-English ports, which I don't track, though there may be some duplicates in there.
In other words, nearly one in twenty ports in the collection. Kudos to the porters for catching most of them. I wonder how many of them were caught as a direct result of the change to -current, 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::
Very true. Keith To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
