<linux/in.h> VS <netinet/in.h>

最新推荐文章于 2024-09-11 21:14:12 发布

花雨的世界

最新推荐文章于 2024-09-11 21:14:12 发布

阅读量2.7k

点赞数 1

分类专栏： Linux

本文链接：https://blog.csdn.net/flowerkitson/article/details/56670445

版权

Linux 专栏收录该内容

0 篇文章

订阅专栏

本文探讨了Linux内核中的头文件 (*.h) 的原始设计目的及其在现代软件开发中的角色转变。早期，这些头文件被用户空间的C库（如libc4和libc5）依赖，用于定义类型、常量等。随着时间发展，标准POSIX头文件成为主流选择，而Linux特有的头文件则更多地服务于底层硬件支持。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

The linux/*.h headers were really meant for internal kernel use and if Linux were being created today, these files would not even exist under /usr/include. But early on, a lot of the userspace libc (libc4 and libc5 at the time) relied on Linux headers to define types, constants, structures, etc. for use in userspace, so netinet/in.h contained just #include <linux/in.h> or similar, and the lovely tradition got started. Today the only headers in the linux tree that should be used for userspace apps are some things related to supporting specific hardware at a low level, like the Linux console, framebuffer, video4linux, etc.

In short, you should use netinet/in.h (the standard header specified by POSIX) and pretend you never saw linux/in.h. :-)