Garrett D'Amore writes: > Then those interfaces should not have been promoted, IMO. Instead, > leave a contract in place, and provide suitable replacements for truly > public consumption that either lack the side effect, or make it clear > that a side effect exists (mcopyandfreemsg().). As I pointed out > earlier, there are cases where that side effect is toxic, and mcopymsg() > cannot be used.
I agree that the current man page documentation is incomplete and should be fixed ... but I do not understand why the function name itself needs to document all possible side-effects. That seems like an unnecessarily high bar to cross. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
