You know I share your opinion that external programming interfaces should be held stable, to whatever extent is reasonable and possible.
I'm certainly arguing for a change here, but it won't hurt my feelings if you don't make the change (it never does).
"Information hiding" is a classic technique for avoiding the need for interface change. This happens to be a case where information could be better hidden, towards the end of avoiding future interface churn. I.e., it may be a "pay me now, or pay me later" situation. I think it's better to make the change now, since you're breaking the interface anyway in 2.17, than to have this come up later, during a time when you want the interface to be stable, and find that you have no choice but to break it again.
If my arm-twisting isn't working, I'll say no more about it... 8^) -John
Dave Grothe wrote:
At 10:58 AM 2/18/2004, John A. Boyd Jr. wrote:
I.e., if drivers break, it's because they're doing something they should never, ever do anyway.
But which they may have been doing for years. One of my complaints about the kernel guys is that they make no attempt to hold the driver-kernel interface constant even through a "stable" version of the kernel. I'm trying not to follow suit here.
-- Dave
------------------------------------------------------------------------
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.591 / Virus Database: 374 - Release Date: 2/17/2004
_______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
