> 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 it's unfortunate that mcopymsg() has a side effect, but the fact is that it was already in widespread use and thus renaming it or otherwise playing paperwork games wouldn't have materially changed things -- we'd still need to define a new function with a different name that doesn't have the side effect. In any case, my point was that your original attack was off the mark, because the interfaces had already leaked out of the consolidation and thus were already sedimented -- as covered in the case materials: Please note that although these interfaces are consolidation-private, that has not always stopped other consolidations from making use of them. Indeed, a quick search shows that both the NWS and NSPG consolidations have drivers which reference some of the interfaces this case proposes to make public. As such, only minor backwards-compatible changes (noted below) have been made to the existing interfaces. -- meem _______________________________________________ networking-discuss mailing list [email protected]
