Messages in this thread | | | Subject | Re: unremovable files and possible fs corruption (2.1.123) | Date | Sat, 31 Oct 1998 22:56:16 -0500 | From | "Brandon S. Allbery KF8NH" <> |
| |
In message <71gldd$jml@pell.pell.portland.or.us>, david parsons writes: +----- | In article <linux.kernel.199810310122.UAA00331@hilfy.ece.cmu.edu>, | Brandon S. Allbery KF8NH <allbery@kf8nh.apk.net> wrote: | >In message <71dep8$ari@pell.pell.portland.or.us>, david parsons writes: | >| david parsons \bi/ Pushing the published kernel interfaces into a shar | ed | >| \/ library is creeping dangerously close to the NT wad | -o- | >| dll's approach. | > | >And what else is libc.so (aside from being one humongous DLL instead of a | >bunch of smaller ones)? | | But that's not the kernel interface, that's simply a collection of | nice wrappers around the kernel interface. | | Today I can write code that avoids libc altogether and continues to | work, but if libc becomes the published interface, that guarantee is | gone. +--->8
*shudder*
I have *never* worked with single platforms. (I got started by being confronted with Xenix and TOPS-20 simultaneously.) As such, portability means a LOT to me, and coding to a particular non-portable interface is Evil. (Which may explain in part why I don't like Microsoft much....)
There are in fact times when it's unavoidable --- an example being the little program that controls iBCS debugging. But they should be rare, and avoided whenever possible.
-- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering KF8NH Kiss my bits, Billy-boy.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |