Re: [RFC] Splitting kernel headers and deprecating __KERNEL__

From: Linus Torvalds
Date: Tue Dec 14 2004 - 13:08:19 EST

On Tue, 14 Dec 2004, Andreas Schwab wrote:
> Linus Torvalds <torvalds@xxxxxxxx> writes:
> > This is a common issue with namespace pollution. For example, this program
> > is perfectly valid afaik (well, except for being _stupid_, but that's
> > another issue):
> >
> > #include <stdio.h>
> >
> > const char *int32_t(int i)
> > {
> > return i ? "non-zero" : "zero";
> > }
> Actually this is not allowed in POSIX. _Any_ header may define any
> identifier ending with "_t".

.. and that's POSIX.

It's not true for BSD_SOURCE, for example.


How hard is it to understand? There are millions of different standards,
many of them without any standards body at all, and just plain standards
by virtue of "that's how people have done it for years".

uint32_t is totally useless for the kernel. We should never ever use it.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at