![]() | |||||||||||
Messages in this thread |
Linus Torvalds <torvalds@osdl.org> 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".
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
| ||||||||||
| Last update: 2005-03-22 14:08 [from the cache] ©2003-2008 | |||||||||||