Re: [patch 1/17] Infrastructure to mark exported symbols as unused-for-removal-soon

[Jörn Engel]

On Tue, 9 May 2006 18:13:00 +0200, Arjan van de Ven wrote:
> Andrew Morton wrote:
> >So hum.  Don't you think it'd be better to look at each API as a whole,
> >make decisions about what parts of it _should_ be offered to modules,
> >rather then looking empirically at which parts presently _need_ to be
> >exported?
> 
> So I think personally it's worth biting the bullet. I expect 95% of those 
> 900 to
> never ever come back. Those 5% will churn, sure. But, to a large degree, 
> the fact
> that there's no user is an indication that the API may well not be right in 
> the
> first place, or not in demand.

[ Your mailer... ]

Rusty once pointed out that Linux doesn't ever implement complete
interfaces like students are usually told to do.  Instead, only
functions that are actually used are implemented.  Among other things,
this makes sure that implemented code is actually tested and works as
advertised.  Unused code, on the other hand, tends to bitrot.

Well, maybe Rusty was wrong and I shouldn't have listened.  But his
points made a lot of sense back then.  Who knows, it might still make
sense.

Jörn

-- 
This above all: to thine own self be true.
-- Shakespeare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/