On Mar 26, 2006, at 16:18:29, Rob Landley wrote:
The problem is things like u64 etc that is VERY common in all
headers, but then again __u64 etc are just fine, history has
proven that already.
Agree. But to be on the safe side one can use uint64_t and friends
(which the kernel can typedef to u64 and first degree relatives)
Now that the kernel no longer targets gcc before 3.2, c99 names are
merely ugly rather than an actual problem. :)
No, they're still a problem in ABI headers because they have defined
visibility. A userspace program that does not include <stdint.h>
will not have those types put in its namespace. Including <sys/
time.h> _cannot_ bring <stdint.> in automatically, that breaks the
POSIX symbol visibility rules.
Cheers,
Kyle Moffett
-
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]
