Rob Landley wrote:
On Sunday 26 March 2006 12:57 pm, Avi Kivity wrote:
This is true for a small enough application. But things grow, libraries
are added, and includes keep pulling other includes in. Sooner or later
you'll have a collision.
And you'll fix it when it happens. Fact of life.
Fixing it will mean breaking either the ABI of the kernel or of the
large library you pulled in.
An ABI bug causes pain far beyond its size. Look at the trouble caused
when some interfaces uses unsigned instead of u64. In kernel APIs, you
just replace the type, but in the ABI, you add a new syscall or do some
other hack.
Much better to get it right the first time, even if it's ugly. It's an
ABI, not a beauty contest nominee.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
